agentleFS
Yeachan-HeoYeachan-Heo/oh-my-claudecode/skills/sdd/SKILL.md

sdd

Skill41k starsChanged 7 days agoMITView on GitHub

Spec-Driven Development. Interview → spec with acceptance criteria → plan → test-first execution. `/sdd full` runs the 6-phase pipeline instead.

22 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about Yeachan-Heo/oh-my-claudecode

The biggest 5 of 81 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 81

Talked about on GitHub, YouTube, Bluesky and the web (81 times).

On GitHub · 50

45 more on GitHub

On YouTube · 20

15 more on YouTube

On Bluesky · 10

5 more on Bluesky

On the web · 1

Used with

Projects with it also use bdd, migrate and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • TashanGKDSkill

    bdd

    行为驱动开发(BDD)流程助手。用 Given-When-Then 描述验收标准,包含 Feature 文件管理、步骤定义实现。用户提到 BDD、验收测试、Gherkin 时使用。

    Also in 3 projects that use this

  • tuistSkill

    migrate

    Migrates existing Xcode projects to Tuist generated workspaces with build and run validation, external dependency mapping, and migration checklists. Use when adopting Tuist for an existing app or converting a hand-edited Xcode project to generated projects.

    Also in 4 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 3 projects that use this

  • Hugging FaceSkill

    implement

    Make tests pass. Invoke after /write-tests produces failing tests.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If several spec/*/ folders exist and the task is unclear, ask which one to resume via AskUserQuestion.

    line 19
  2. Distinctive:

    Read the code first; never ask what the code answers.

    line 26
  3. Distinctive:

    Ask only if the answer changes behavior, scope, or a safe assumption.

    line 28
  4. Distinctive:

    Stop when an implementer would have no questions left.

    line 29
  5. Distinctive:

    No implementation details, no "fast"/"correct" without a number.

    line 42
  6. Distinctive:

    Every AC appears in at least one task.

    line 51
  7. Distinctive:

    Write tests for the task's ACs.

    line 60
  8. Distinctive:

    If still failing after 2 different attempts, stop and report: what failed, what you tried, 2 options, your recommendation.

    line 62

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

SDD (lite)

Interview → Spec+AC → Plan → Test-first execute. Artifacts live in spec/<slug>/ at project root (one folder per feature). No implementation code before spec/<slug>/plan.md is approved.

If args start with full: read and follow phases/spec.md, phases/criteria.md, phases/rules.md, phases/review.md, phases/tasks.md, phases/execute.md (relative to this skill's directory) in that order, confirming with the user after each artifact. Pick the slug as in Entry; every phase writes to spec/<slug>/. Then stop reading this file.

Entry

  1. git status --short --branch; list spec/*/.
  2. Pick the slug (kebab-case, max 40 chars, descriptive of the feature):
    • On a feature branch, use the branch name without the prefix (feat/csv-export → csv-export) if spec/<that>/ exists or the task matches it.
    • Otherwise derive it from the task (add CSV export of reports → csv-report-export) and show it to the user in the first message so they can correct it.
    • If several spec/*/ folders exist and the task is unclear, ask which one to resume via AskUserQuestion.
  3. Resume at the first missing artifact in spec/<slug>/ and say where you resume.
  4. Task text comes from args or the user's message. Ask only if there is none.
  5. Skip the flow for tasks prefixed quick:.

1. Interview (no file yet)

  • Read the code first; never ask what the code answers.
  • One question at a time via AskUserQuestion: 2-4 concrete options, a recommended pick, one-line reason why it matters.
  • Ask only if the answer changes behavior, scope, or a safe assumption. Otherwise decide and record it as an assumption.
  • Stop when an implementer would have no questions left. Typically 3-7 questions; more means the task should be split.

2. Spec → spec/<slug>/spec.md

One file, short:

  • Summary (2-3 sentences)
  • Decisions and assumptions (bullets, with the reason)
  • Out of scope
  • Acceptance criteria: AC-1, AC-2, ... one observable outcome each, EARS form: When <trigger>, the <system> shall <response>. / If <bad trigger>, then the <system> shall <response>. / While <state>, ...
    • Bounded values: three ACs (inside, at, beyond the bound).
    • Error paths: state the response and whether it is all-or-nothing.
    • No implementation details, no "fast"/"correct" without a number.

Show a 5-line summary, then AskUserQuestion: continue or revise.

3. Plan → spec/<slug>/plan.md

  • Design in under 10 lines: components, flow, new dependencies. Record only deviations from project conventions (read CLAUDE.md, build files, existing layout first) and deliberate "not using X" decisions.
  • Tasks as a checklist, ordered, each under ~1 hour: - [ ] T1: <what> (AC-1, AC-2) — verify: <test or command>
  • Group into phases (max 4); end each phase with CHECKPOINT.
  • Every AC appears in at least one task. Self-check this; if something is unclear, go back to the interview instead of guessing.
  • For large or risky features only (many ACs, migrations, new infra), add a "Risks" list of up to 5 items with mitigations.

Show the plan, AskUserQuestion: approve or revise.

4. Execute (test-first)

Per task, in order, no skipping:

  1. Write tests for the task's ACs; run them; confirm they fail for the right reason (red).
  2. Implement the minimum to pass (green); run the full test suite, type check, and linter.
  3. If still failing after 2 different attempts, stop and report: what failed, what you tried, 2 options, your recommendation.
  4. Tick the task in plan.md (- [x]). Do not edit spec.md during execute; if the spec is wrong, stop and say so.

At each CHECKPOINT: report tasks done, ACs satisfied (AC → test file), test/lint results. Then wait for the user: ok, revise T<n>: ..., or rollback T<n>.

At the end: AC coverage table (AC → test) and one command to run the tests.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.