Contract
- Input: user intent, plus the repository constitution (or the intent to create one).
- Output:
SpecDrivenArtifacts covering constitution, spec, plan, tasks, and verification.
- Scope: SDD is the planning spine. Implementation belongs to
implement; this skill produces the artifacts implementation is held against.
- Rule: no phase starts until the previous artifact is durable. Ambiguity is resolved with
grill-with-docs, not guessed.
The constitution
The constitution is the repo-local rule set SDD enforces: architecture invariants, stack constraints, quality bar, validation commands, and the non-negotiables (security, privacy, accessibility). It lives at docs/spec/constitution.md and is versioned like code. Create it once with grill-with-docs; every spec and plan is checked against it.
Phases
- Specify (
/specify compatible). Turn intent into a spec: problem, goals, user stories, acceptance criteria, explicit non-goals. The spec is the source of truth; the plan and tasks must trace to it.
- Plan (
/plan compatible). Architecture and seams: components, data flow, the public API seam, trade-offs as ADR candidates, and the validation strategy. Every decision traces to a constitution rule.
- Tasks (
/tasks compatible). Decompose the plan into tracer-bullet tasks: narrow, complete paths through behavior, validation, and delivery. Each task names its spec clause and its acceptance evidence. In the quirk flow this phase is to-spec followed by to-tickets; the SDD artifacts carry the same contracts.
- Implement. Hand the tasks to
implement; each slice validates against its acceptance criteria.
- Verify. Run
analyze-artifacts to confirm spec, plan, tasks, and implementation still agree. Divergence is a finding, not a footnote.
Provenance
| Question |
Answer |
| What is the source of truth? |
User intent, the repository constitution, and the existing stack and tracker |
| What is in scope? |
Constitution, specify, plan, tasks, implement handoff, verify |
| What is explicitly out of scope? |
Implementation itself, which belongs to implement against these artifacts |
| Who or what consumes this artifact afterward? |
implement for each task slice, then analyze-artifacts for verification |
| What evidence proves it is done? |
SpecDrivenArtifacts with constitution, spec, plan, tasks, and verification |
| What risk remains? |
Tasks that trace to no spec clause; a plan without declared seams |
Artifact
SpecDrivenArtifacts with status, constitution, spec, plan, tasks, verification, nextConsumer, and riskRemaining.
Reference
- The canonical prompt for this skill is versioned at
.agents/skills/prompts/spec-driven-development/v1.md (prompt version 1.0).
- Governing skills: see the dependencies in the frontmatter for the skills this one composes with.
Every execution is traced via record-execution.mjs. The trace includes traceId, spanId, model tier, duration, tool calls, and quality score.
Rationale
Vibe coding produces implementations no artifact can be held against. A constitution plus durable specify/plan/tasks artifacts gives every implementation a source of truth to trace to, which is what makes review and repair possible instead of ornamental.
Completion
- The constitution exists and the spec, plan, and tasks trace to it.
- Every task names the spec clause it implements and the evidence that proves it.
analyze-artifacts reports no unresolved divergence.
- No approval is required for SDD artifacts: the constitution, spec, plan, and tasks are repo-local documentation files, reversible via git.
Failure modes
- Spec without a constitution: the plan has no rule set to be checked against; write the constitution first.
- Tasks without spec clauses: a task that traces to nothing is scope creep in waiting.
- Plan without seams: an implementation without a declared public seam cannot be reviewed against the plan.
@include .agents/skills/platform/contract-base.xml
1---2name: "spec-driven-development"3category: "project"4maturity: "experimental"5version: "1"6description: "Run spec-driven development (SDD): a constitution for repo-local rules, then specify, plan, and tasks as durable artifacts, then implement against them - compatible with GitHub Spec Kit's /specify, /plan, /tasks workflow."7license: "MIT"8capabilities:9 - produce a spec artifact from intent (specify phase)10 - produce a plan artifact with architecture and seams (plan phase)11 - decompose the plan into tracer-bullet tasks (tasks phase)12 - verify implementation against the spec and plan13 - trace spec driven development decisions across inputs, constraints, and failure paths14 - validate project outcomes with evidence, assumptions, and explicit next steps15inputs:16 - the user's intent for a feature or change17 - the repository constitution (or the intent to create one)18 - the existing stack, tracker, and validation commands19outputs:20 - type: object21 name: SpecDrivenArtifacts22 properties:23 status: { type: string, enum: [specified, planned, tasked, implemented, blocked] }24 constitution: { type: "string" }25 spec: { type: "string" }26 plan: { type: "string" }27 tasks: { type: "array", items: { type: "string" } }28 verification: { type: "object" }29 nextConsumer: { type: "string" }30 riskRemaining: { type: "string" }31 required: [status, nextConsumer]32sideEffects:33 - write-docs34 - write-files35dependencies:36 - to-spec37 - to-tickets38 - grill-with-docs39 - implement40 - analyze-artifacts41 - docs-adrs42stopCondition: "Constitution, spec, plan, and tasks exist as durable artifacts and the implementation verifies against them."43risk: "medium"44trustTier: "3"45maxIterations: "12"46promptVersion: "1.0"47artifactType: "spec-driven-artifacts"48modelTier: "reasoning"49evaluators: ["behavioral", "regression"]50fixturesPath: .agents/skills/platform/fixtures/behavioral/spec-driven-development.json51diataxis: "how-to"52tags: ["spec-driven", "sdd", "spec-kit", "constitution", "planning"]53compatibility:54 - claude-code55 - codex56 - opencode57approvalRequired: "false"58approvalFor: []59metadata:60 source: https://skillmd.com/skills/quantumquirkxyz/spec-driven-development61---6263## Contract6465- Input: user intent, plus the repository constitution (or the intent to create one).66- Output: `SpecDrivenArtifacts` covering constitution, spec, plan, tasks, and verification.67- Scope: SDD is the planning spine. Implementation belongs to `implement`; this skill produces the artifacts implementation is held against.68- Rule: no phase starts until the previous artifact is durable. Ambiguity is resolved with `grill-with-docs`, not guessed.6970## The constitution7172The constitution is the repo-local rule set SDD enforces: architecture invariants, stack constraints, quality bar, validation commands, and the non-negotiables (security, privacy, accessibility). It lives at `docs/spec/constitution.md` and is versioned like code. Create it once with `grill-with-docs`; every spec and plan is checked against it.7374## Phases75761. **Specify** (`/specify` compatible). Turn intent into a spec: problem, goals, user stories, acceptance criteria, explicit non-goals. The spec is the source of truth; the plan and tasks must trace to it.772. **Plan** (`/plan` compatible). Architecture and seams: components, data flow, the public API seam, trade-offs as ADR candidates, and the validation strategy. Every decision traces to a constitution rule.783. **Tasks** (`/tasks` compatible). Decompose the plan into tracer-bullet tasks: narrow, complete paths through behavior, validation, and delivery. Each task names its spec clause and its acceptance evidence. In the quirk flow this phase is `to-spec` followed by `to-tickets`; the SDD artifacts carry the same contracts.794. **Implement.** Hand the tasks to `implement`; each slice validates against its acceptance criteria.805. **Verify.** Run `analyze-artifacts` to confirm spec, plan, tasks, and implementation still agree. Divergence is a finding, not a footnote.8182## Provenance8384| Question | Answer |85|---|---|86| What is the source of truth? | User intent, the repository constitution, and the existing stack and tracker |87| What is in scope? | Constitution, specify, plan, tasks, implement handoff, verify |88| What is explicitly out of scope? | Implementation itself, which belongs to `implement` against these artifacts |89| Who or what consumes this artifact afterward? | `implement` for each task slice, then `analyze-artifacts` for verification |90| What evidence proves it is done? | SpecDrivenArtifacts with constitution, spec, plan, tasks, and verification |91| What risk remains? | Tasks that trace to no spec clause; a plan without declared seams |9293## Artifact9495`SpecDrivenArtifacts` with `status`, `constitution`, `spec`, `plan`, `tasks`, `verification`, `nextConsumer`, and `riskRemaining`.9697## Reference9899- The canonical prompt for this skill is versioned at `.agents/skills/prompts/spec-driven-development/v1.md` (prompt version 1.0).100- Governing skills: see the dependencies in the frontmatter for the skills this one composes with.101102Every execution is traced via `record-execution.mjs`. The trace includes traceId, spanId, model tier, duration, tool calls, and quality score.103104## Rationale105106Vibe coding produces implementations no artifact can be held against. A constitution plus durable specify/plan/tasks artifacts gives every implementation a source of truth to trace to, which is what makes review and repair possible instead of ornamental.107108## Completion109110- The constitution exists and the spec, plan, and tasks trace to it.111- Every task names the spec clause it implements and the evidence that proves it.112- `analyze-artifacts` reports no unresolved divergence.113- No approval is required for SDD artifacts: the constitution, spec, plan, and tasks are repo-local documentation files, reversible via git.114115## Failure modes116117- Spec without a constitution: the plan has no rule set to be checked against; write the constitution first.118- Tasks without spec clauses: a task that traces to nothing is scope creep in waiting.119- Plan without seams: an implementation without a declared public seam cannot be reviewed against the plan.120121---122@include .agents/skills/platform/contract-base.xml