Spec

Use when the user wants a spec-driven development workflow for implementing a feature in the current codebase, from fuzzy idea or existing active spec through requirements, technical plan, tasks, implementation, verification, and closure report. Auto-detects project/spec state, writes persistent files under specs/, asks one grounded question at a time when requirements are ambiguous, and stops at stage gates. NOT for stakeholder PRDs (prd-create), ADO ticket breakdown (prd-breakdown), single architecture-decision records (adr), or already-frozen tasks that should simply be implemented.

80 stars 13 forksProductivity & Notes

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add KerberosClaw/kc_ai_skills --skill spec
Manual install
git clone --depth 1 https://github.com/KerberosClaw/kc_ai_skills.git /tmp/kc_ai_skills
mkdir -p ~/.claude/skills
cp -r /tmp/kc_ai_skills/spec ~/.claude/skills/spec

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# /spec — Spec-Driven Development

You are a spec-driven development lead. You turn a user feature request into persistent requirements, implementation plan, task checklist, verified code, and a closure report while respecting the current repository state.

把「實作 feature 的流程」標準化:需求釐清 → 技術審查 → 實作 → 驗收 → 結案。
一個入口,自動判斷該做什麼。

## 使用方式

```
# 新需求(有明確想法)
/spec 做一個 Markdown loader,遞迴讀取資料夾內所有 .md 檔

# 新需求(很模糊)
/spec 我想做一個全本地的 RAG pipeline

# 繼續上次進度(自動偵測狀態)
/spec

# 指定操作特定 spec
/spec check 01-loader-chunker
/spec report 01-loader-chunker
```

---

## 執行規則

1. 永遠先跑 **Stage Detection** 判斷目前狀態,再決定進入哪個階段。
2. spec/plan/tasks/report 放在專案根目錄的 `specs/` 下;Discovery 的 DESIGN 與接入 ADR 的文件位置沿用各自階段及 repo 慣例。
3. 用 `git rev-parse --show-toplevel` 找專案根目錄。如果不在 git repo 裡,用當前工作目錄。
4. 不主動執行 user 沒要求的事。每個階段完成後說明產出;已有完整執行授權時不重問相同授權,沒有才問下一步。無人值守沿 dispatch 的授權與停止條件,不自行擴張。
5. 與 user 的互動用正體中文。spec/plan/tasks/report 文件摘要為英文(English summary),內容為正體中文。
6. **判準不在本檔。** 「怎樣才算過」寫在 `references/`,文件格式寫在 `templates/`。下面各階段寫到「先讀」的地方,一定要真的讀那份檔再做,不要憑印象。每個階段結束都用 [references/review.md](references/review.md)「完成狀態」的用字回報。
7. **技術決策需要記錄時接 ADR,再返回原階段。** 設計或實作中形成重要決策時,先讀已安裝的 `adr`(同套件:[adr/SKILL.md](../adr/SKILL.md)),依 repo 慣例與其判準決定是否記錄;不另抄判準、不每個 task 都開 ADR。只記錄已確定的決策,先查重,將結果引用回 DESIGN/plan/tasks;不需要 ADR 就留在原計畫。未決或超出授權的改動先回 user,不能藉 ADR 批准自己。
Read the full skill on GitHub

Details

Skill name
spec
Path
spec/SKILL.md
License
MIT
Repo updated
14 November 2026

FAQ

What does the Spec skill do?

Use when the user wants a spec-driven development workflow for implementing a feature in the current codebase, from fuzzy idea or existing active spec through requirements, technical plan, tasks, implementation, verification, and closure report. Auto-detects project/spec state, writes persistent files under specs/, asks one grounded question at a time when requirements are ambiguous, and stops at stage gates. NOT for stakeholder PRDs (prd-create), ADO ticket breakdown (prd-breakdown), single architecture-decision records (adr), or already-frozen tasks that should simply be implemented.

How do I install the Spec skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add KerberosClaw/kc_ai_skills --skill spec. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Spec popular?

It lives in KerberosClaw/kc_ai_skills, which has 80 GitHub stars and 13 forks, and is included in 1 curated skill list.

Related skills

Adr

80

KerberosClaw/kc_ai_skills

Use when a durable technical decision was just made in conversation and should be recorded, or when user asks to write/record an ADR (開 ADR / 記個決策 / 這要不要 ADR). Runs a three-gate check FIRST and actively talks the user out of writing one when the decision doesn't qualify — then writes a lightweight (title + 1-3 sentences) ADR following the repo's own ADR conventions if any exist. Repo conventions always override this skill's defaults. NOT for requirement specs (spec / prd-create) or rewriting historical decisions; preserve their text, allow evidence-backed current-state notes, and record change

Writing & ContentIn 1 list13

Align

80

KerberosClaw/kc_ai_skills

Reconcile existing repository documentation with the current implementation, especially after verified hotfixes or after QA in an unattended task. A manual run first asks whether to align only the docs a specific change touched (trigger scope) or rescan the whole repo; unattended runs use the scope the dispatch states and default to the whole repo. Follow cross-repo references for evidence; edit only documentation in the authorized repo, annotating conflicting historical records. Not for fixing code, deploying, inventing requirements, or building a new documentation suite.

Writing & ContentIn 1 list13

Character Lora

80

KerberosClaw/kc_ai_skills

Use when the user wants to build a consistent-identity LoRA for an original character — defining the character, generating a face/body-consistent multi-angle dataset (via the gpt-image-gen skill for codex image generation), captioning it, doing base-specific homework, training on a chosen base (Pony / Z-Image / others) on a local GPU, and producing a usable LoRA. This skill ORCHESTRATES the end-to-end pipeline and gates every expensive/irreversible step; it delegates actual image generation to gpt-image-gen and never improvises training settings from memory.

Images, Video & AudioIn 1 list13

Workflow Router

80

KerberosClaw/kc_ai_skills

Use when the user is unsure which engineering workflow skill to use: discussion, dispatch or code review, a full spec lifecycle, PRD/ADO, ADR, debugging, documentation, QA or release readiness. Choose the smallest applicable route, explain it, then hand off. The router does not author artifacts or execute tasks itself.

Productivity & NotesIn 1 list13

Reproducing CI Locally

115

wdm0006/python-skills

Run the CI gate on your machine so it agrees with the runner — deriving the exact command, paths, markers, and env from the workflow file instead of the Makefile, unblocking gate steps that short-circuit and hide the next failure, pinning the linter version CI resolves, building the interpreter/toolchain environment the runner builds, and confirming the run is green instead of explaining a red job away. Use when a check passes locally but fails in CI (or the reverse), when a lint/format job goes red on an untouched file, when setting up a local dev loop for an unfamiliar repo, or before pushin

Productivity & Notes18

Wp Wpcli and Ops

116

jorgerosal/wordpress-skills

WordPress WP-CLI and operations review guidance. Use when reviewing WP-CLI commands, search-replace plans, multisite operations, cron or cache maintenance, deployment scripts, operational runbooks, CLI automation, or when user mentions "WP-CLI", "search-replace", "multisite ops", "wp cron", "wp db", "deployment script", "maintenance task", "CLI command", or "ops review". Helps review command safety, environment targeting, multisite scope, automation reliability, and operational blast radius in WordPress codebases and runbooks.

Productivity & Notes13

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.