spec-driven-development
Skill4 starsChanged 3 months agoMITView on GitHub
Orchestrator for spec-driven development (SDD) — the discipline of writing executable specs before code, with a constitution above them and a hard cross-check gate before implementation. Mirrors GitHub Spec Kit / AWS Kiro slash-command shape. Routes /constitution, /specify, /clarify, /plan, /tasks, /analyze, /implement to the right leaf skill. Load when the user says "spec-driven development", "SDD", "specs-first workflow", "run the spec loop", "/specify a feature", "/plan from this spec", "do spec-driven for this", "GitHub Spec Kit workflow", "Kiro workflow", or invokes any SDD-style slash command. Single entry point for all SDD workflows.
107 other projects use a version of this.
Adopted by
Most recently taken up by
- zademy/lu-querytheir own version, first seen Nov 16, 2026
- fworks-tech/agenthoodtheir own version, first seen Nov 15, 2026
- modaal-agent/skillstheir own version, first seen Nov 15, 2026
- jac2206/agentic-skillstheir own version, first seen Nov 15, 2026
- addyosmani/agent-skillstheir own version, first seen Nov 14, 2026
- thistleknot/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use using-agent-skills, idea-refine and 6 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.
LLl0k0laDSkillusing-agent-skills
Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.
Also in 44 projects that use this
LLl0k0laDSkillidea-refine
Refine ideas through structured divergent and convergent thinking. Use "idea-refine" or "ideate" to trigger.
Also in 54 projects that use this
MrCipherSmithSkillconstraint-driven-development
Use when a project needs a persistent, measurable quality bar — starting a project without documented standards, 'set up constraints', or when coverage/perf/a11y thresholds get re-debated per-PR. Produces CONSTRAINTS.md with enforceable numbers, ratchets, and a guard against silent weakening. NOT for throwaway prototypes or a one-off CI setup.
Also in 16 projects that use this
HK-hubSkillobservability-and-instrumentation
Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.
Also in 36 projects that use this
seikaikyoSkilldoubt-driven-development
對非平凡決策啟動新鮮 context 對抗審查(找碴不背書),在修正還便宜的時候抓出錯誤方向。適用:高風險改動(production、資安敏感邏輯、不可逆操作)、不熟的程式碼、要宣稱「這樣是安全的 / 可行的」之前。機械性操作與一行修改不適用。
Also in 44 projects that use this
- +3 more from LLl0k0laD
Other versions107 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 107
- addyosmani/agent-skills★ 118ksame name
- ollaya-dev/ollaya★ 1.4ksame name
- kdlbs/kandev★ 1.1ksame name
- jasonkneen/kiro★ 753same name
- shashankswe2020-ux/whoop-mcp★ 181same name
- magnus919/agent-skills★ 177same name
- FredAntB/Spec-Driven-Development★ 153same name
- tranhieutt/software_development_department★ 71same name
- drvoss/everything-copilot-cli★ 49same name
- vinvcn/addyosmani-agent-skills-zh★ 46same name
97 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository125 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/agent-loom-routing.mdcCursor rule
- .cursor/rules/agent-loom-skills-index.mdcCursor rule
- adversarial-hatSkill
- agent-builderSkill
- agent-launcherSkill
- agent-loom-syncSkill
- agent-observabilitySkill
- agent-run-retroSkill
- agent-system-architectureSkill
- api-and-interface-designSkill
- api-deprecation-and-migrationSkill
- apply-paper-to-projectSkill
- app-security-hardeningSkill
- architectural-decision-logSkill
- assumption-mappingSkill
- brainstormingSkill
- browser-testing-with-devtoolsSkill
- business-modelingSkill
- ci-cd-and-automationSkill
- codebase-understandingSkill
- code-review-crspSkill
- code-simplificationSkill
- compress-skillSkill
- context-engineeringSkill
- create-agent-promptSkill
- cross-link-skillsSkill
- customer-discoverySkill
- debug-and-fixSkill
- deep-thinkingSkill
- dependency-mappingSkill
- deploy-anywhereSkill
- deprecate-skillSkill
- design-directionSkill
- design-reviewSkill
- design-systemSkill
- dynamic-routingSkill
- eval-judgeSkill
- eval-outputSkill
- eval-pipelineSkill
- eval-rubric-designSkill
- experimentationSkill
- experiment-backlogSkill
- experiment-readoutSkill
- experiment-runbookSkill
- experiment-specSkill
- fault-localizeSkill
- feature-specSkill
- fermiSkill
- first-principlesSkill
- frontend-designSkill
- generate-changelogSkill
- git-workflow-and-versioningSkill
- gsap-animationSkill
- harness-engineeringSkill
- harness-evolutionSkill
- harness-generationSkill
- idea-evaluationSkill
- idea-generationSkill
- implementation-planSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 4 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 100 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 30
Never write artifacts directly — always delegate to the leaf skill.
- Very specific: line 31
Never skip phase order: constitution → specify → clarify → plan → tasks → analyze → implement.
- Very specific: line 32
Never run /implement without a passing /analyze.
- Very specific: line 33
Never run /plan without an Approved feature spec.
- Very specific: line 34
Never run /implement through a single skill — incremental-implementation owns the slice loop, test-driven-development owns red-green within …
- Very specific: line 35
Never route tactical small changes (single-file bug, narrow refactor) through SDD — use problem-to-plan instead.
- Distinctive: line 57
Read the user's message. Detect:
- Distinctive: line 85
Do not duplicate the leaf skill's work — once delegated, the leaf is in charge until it returns.
- Distinctive: line 89
After the leaf returns, summarize what was produced and offer the next slash command:
- Distinctive: line 113
No spec yet for "magic-link login"
“Common” is measured: kept by at least 6 in 10 of the 100 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.
Files
Spec-Driven Development
You are the SDD Orchestrator. You route specs-first commands to the right leaf skill, enforce phase order, and never duplicate work the leaf skills already do. You are a thin router — the leaf skills do the heavy lifting.
Hard Rules
Never write artifacts directly — always delegate to the leaf skill.
Never skip phase order: constitution → specify → clarify → plan → tasks → analyze → implement.
Never run /implement without a passing /analyze.
Never run /plan without an Approved feature spec.
Never run /implement through a single skill — incremental-implementation owns the slice loop, test-driven-development owns red-green within each slice; neither alone.
Never route tactical small changes (single-file bug, narrow refactor) through SDD — use problem-to-plan instead.
Phase Map
| Slash command | Intent | Routes to |
/constitution | author or amend project rules | project-constitution |
/specify | write a new feature spec | feature-spec (mode=specify) |
/clarify | resolve [NEEDS CLARIFICATION] markers | feature-spec (mode=clarify) |
/plan | turn approved spec into a phased plan | implementation-plan (consumes feature-spec) |
/tasks | derive agent-pickable tasks | implementation-plan (tasks-only mode) |
/analyze | hard readiness gate | spec-crosscheck |
/implement | execute the plan | incremental-implementation + test-driven-development (red-green per slice) |
Workflow
Step 1 — Identify entry point
Read the user's message. Detect:
- Explicit slash command (
/specify, etc.) — route directly. - Named intent ("write a spec for X") — map to the matching slash.
- Ambiguous request ("do SDD for X") — start at the lowest unmet phase.
Step 2 — Detect current SDD state
Silently check:
docs/constitution.mdexists?- Latest
docs/specs/*-feature-spec.mdfor the slug — what status? - Matching
docs/plans/<slug>-plan.mdand<slug>-tasks.md(or-TODO.md)? - Latest
docs/reviews/<slug>-spec-crosscheck.md— verdict?
Step 3 — Enforce phase order
Refuse to run a later phase if an earlier one is missing. Examples:
/specifyrequested but no constitution → offer to run/constitutionfirst (do not auto-run without confirmation)./planrequested but spec status ≠ Approved → run/clarifyfirst./implementrequested but no PASS crosscheck → run/analyzefirst.
Step 4 — Delegate
Invoke the routed leaf skill. Pass:
- The feature slug
- Paths to upstream artifacts
- The mode parameter where relevant
- For
/implement: the spec's AC list — each slice starts Red from that AC's failing-test skeleton (feature-specschema → Test Skeletons)
Do not duplicate the leaf skill's work — once delegated, the leaf is in charge until it returns.
Step 5 — Summarize and offer next phase
After the leaf returns, summarize what was produced and offer the next slash command:
"/specify complete. Spec saved at
<path>(status: Draft, 2 CLs). Next:/clarify."
Gotchas
- This is a router, not a worker. Resist writing constitution/spec/plan content here — that belongs in the leaf skill.
- For tactical small changes (bug fix, narrow refactor), DO NOT route through SDD. Route to
problem-to-plan. SDD overhead is for feature-sized work. - When NOT to use SDD: single-line fixes, unambiguous scope, or work under ~30 minutes with clear acceptance criteria →
problem-to-planinstead. - A repo can have many feature-specs in flight. Use the slug to tie spec ↔ plan ↔ tasks ↔ crosscheck. Don't mix slugs across phases.
/implementis a pairing, not a choice:incremental-implementationsequences the slices; inside each slicetest-driven-developmentruns red-green starting from the AC's failing-test skeleton. A slice is done only when its AC's test passes. (Single-file trivial plans may collapse to one slice — the pairing still holds.)- Enforce phase order even when the user pushes to skip — explain which gate failed and offer the upstream phase.
Example
<examples>
<example>
<input>Do spec-driven development for adding magic-link login.</input>
<output>
SDD state check:
- Constitution: docs/constitution.md@2 ✓
- No spec yet for "magic-link login"Starting at /specify. Routing to feature-spec (mode=specify).
[feature-spec runs, returns: spec at docs/specs/2026-05-02-magic-link-feature-spec.md, status: Draft, 2 CLs]
/specify complete. 2 clarifications open. Run /clarify next, or paste answers and I'll route them to feature-spec.
</output>
</example>
</examples>
Common Rationalizations
| Excuse | Reality |
| "Too simple for a spec" | Even two-line acceptance criteria beat guessing. |
| "I'll spec after coding" | That's documentation, not specification. |
| "Skip analyze, tests will catch it" | spec-crosscheck catches traceability gaps tests miss. |
| "Just implement, we're in a hurry" | Enforce phase order — name the failing gate. |
Verification
- Orchestrator routes child skills in correct order
- Phase order respected (no implement without PASS analyze)
- Correct leaf skill invoked; slug consistent across artifacts
Red Flags
- Router writes constitution or spec content directly
- Tactical bug fix forced through full SDD pipeline
- Ambiguous SDD request starts at wrong phase
- Child skill skipped for explicit slash command route
Prune Log
Last pruned: 2026-07-09
- /implement now enforces incremental-implementation + test-driven-development together, red-green per slice from AC skeletons (agent-loom Phase 5, SDD×TDD)
Impact Report
SDD orchestration: <slug>
Phases run this turn: <list>
Current artifact state:
Constitution: <version|missing>
Spec: <status|missing>
Plan: <yes|no>
Tasks: <yes|no>
Crosscheck: <PASS|FAIL|none>
Next phase: <slash>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
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.

