GitHub Spec Kit commands will use stakeholder documentation to help generate the constitution.md, spec.md, and plan.md files.

Commands

Initialize speckit

specify init --here

Constitution

/speckit.constitution --text "Code projects emphasize security, maintainability, and code quality. Ensure that all principles are specific, actionable, and relevant to the project context." --files StakeholderDocuments/ProjectGoals.md StakeholderDocuments/AppFeatures.md StakeholderDocuments/TechStack.md

Spec

/speckit.specify --text "MVP RSS reader: a simple RSS/Atom feed reader that demonstrates the most basic capability (add subscriptions) without the complexity of a production-ready application." --files StakeholderDocuments/ProjectGoals.md StakeholderDocuments/AppFeatures.md

Plan

/speckit.plan --files StakeholderDocuments/ProjectGoals.md StakeholderDocuments/TechStack.md

Tasks

/speckit.tasks

Implement

/speckit.implement Implement the MVP First strategy

/speckit.implement Phase 4: User Story 2 - View Subscription List

/speckit.implement Implement tasks in phase 5.

---

Sequential workflow example

GitHub Spec Kit supports iterative development through command chaining. After generating initial specifications, you can refine them progressively:

1. Generate initial spec: /speckit.specify.
2. Identify gaps: /speckit.clarify.
3. Update spec based on answers.
4. Create implementation plan: /speckit.plan.
5. Verify consistency: /speckit.analyze.
6. Generate tasks: /speckit.tasks.
7. Implement incrementally: /speckit.implement.

At any point, if requirements change, you can return to earlier phases, update artifacts, and regenerate downstream artifacts. If a stakeholder changes their mind about file size limits after you generate tasks, you update spec.md, regenerate plan.md to reflect architectural implications, regenerate tasks.md with updated validation steps, then update implementation code.