Skip to content

Commit e171536

Browse files
authored
Add Spec-Driven Development workflow documentation
This file outlines the Spec-Driven Development workflow using the speckit toolset, detailing the sequence of commands and core rules for implementation.
1 parent 1adb19d commit e171536

1 file changed

Lines changed: 45 additions & 0 deletions

File tree

templates/commands/skill.md

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,45 @@
1+
---
2+
name: "speckit"
3+
description: "Full Spec-Driven Development (SDD) workflow powered by github/spec-kit. Use speckit-specify to start a feature, then speckit-plan, speckit-tasks, and speckit-implement in sequence."
4+
metadata:
5+
author: "github-spec-kit"
6+
source: "https://github.com/github/spec-kit"
7+
version: "1.0.0"
8+
---
9+
10+
# Spec Kit — Spec-Driven Development
11+
12+
This skill provides the complete Spec-Driven Development workflow from [github/spec-kit](https://github.com/github/spec-kit).
13+
Individual commands are available as separate skills in this directory — each one maps to a phase of the SDD process.
14+
15+
## Workflow Order
16+
17+
Always follow this sequence — never skip phases:
18+
19+
1. **speckit-constitution** — Establish project governing principles *(run once per project)*
20+
2. **speckit-specify** — Turn a feature description into a structured spec
21+
3. **speckit-clarify** — Resolve ambiguities before planning *(optional but recommended)*
22+
4. **speckit-plan** — Create a phased technical implementation plan
23+
5. **speckit-analyze** — Cross-artifact consistency check *(optional, run after tasks)*
24+
6. **speckit-tasks** — Break the plan into ordered, executable tasks
25+
7. **speckit-implement** — Execute tasks one by one
26+
8. **speckit-checklist** — Post-implementation quality checklist
27+
28+
## Core Rules
29+
30+
- Read `.specify/memory/constitution.md` before every coding decision
31+
- Show the spec summary to the user and wait for approval before planning
32+
- Show task count to the user and wait for approval before implementing
33+
- Use `.specify/scripts/bash/` (Linux/macOS) or `.specify/scripts/powershell/` (Windows) for all file and branch operations
34+
- Never create, move, or delete files in `specs/` without explicit user instruction
35+
36+
## Key File Locations
37+
38+
| File | Purpose |
39+
|------|---------|
40+
| `.specify/memory/constitution.md` | Project governing principles — read before every decision |
41+
| `specs/<feature>/spec.md` | Feature specification created by `speckit-specify` |
42+
| `specs/<feature>/plan.md` | Implementation plan created by `speckit-plan` |
43+
| `specs/<feature>/tasks.md` | Task breakdown created by `speckit-tasks` |
44+
| `.specify/templates/` | Base templates for spec, plan, tasks, and checklist artifacts |
45+
| `.specify/scripts/` | Automation scripts for branch and file management |

0 commit comments

Comments
 (0)