Use the Governed Spec project template in Manager, inspired by GitHub Spec Kit: write a constitution once, then take every feature through specify, clarify, plan, tasks, analyze and implement.
Testing, architecture and convention rules live in one short constitution. Every spec, plan and task is checked against it.
The spec captures prioritized user stories, requirements and success criteria. Technology choices wait for the plan.
Clarify removes ambiguity before planning; analyze cross-checks spec, plan and tasks before any code is written.
Spec Kit makes the specification the source of the code: define what and why, then decide how. The specify CLI (specify init) sets up a repository, and /speckit.constitution writes the principles to .specify/memory/constitution.md.
Per feature, /speckit.specify, /speckit.plan and /speckit.tasks write spec.md, plan.md and tasks.md under specs/, /speckit.implement builds it and /speckit.converge appends remaining work. Optional gates: /speckit.clarify before planning and /speckit.analyze, a read-only check where constitution conflicts are critical.
Adapted from GitHub Spec Kit, MIT © GitHub, Inc. (github.com/github/spec-kit). Not affiliated with or endorsed by GitHub.
Where each Spec Kit command and artifact lives in your project.
| Spec Kit | In Manager |
|---|---|
| constitution.md | The constitution skill, plus your principles on a wiki page or in the project description. |
| Feature folder (specs/001-name/) | A Feature work item; the Features saved filter lists them all. |
| spec.md, plan.md | The Feature's description or linked wiki pages. |
| [NEEDS CLARIFICATION] | The Needs-Clarify label on the Feature while questions are open. |
| tasks.md, [P] marker | Task children with a User Story field; parallel tasks get the [P] label. |
| Analyze report | A comment on the Feature; breaches get the Constitution-Violation label. |
| /speckit.* commands | One skill per command, mirrored in the Feature statuses. |
Connect your agent over MCP and have it create a project from the Governed Spec template.
Say to your agentManager: Create a project from the Governed Spec template and ask me what we are building.
Agree on your non-negotiable principles: testing, architecture, conventions, performance and UX bars. Keep them short; a rule you will not enforce does not belong.
Say to your agentManager: Run the constitution skill, ask me about our principles and put them on a wiki page.
The specify skill writes prioritized user stories, requirements and success criteria. The clarify skill asks about gaps, and the Feature carries Needs-Clarify until they are answered.
Say to your agentManager: Run the specify skill for my next feature, then clarify the open questions with me.
The plan skill decides the how and checks it against the constitution. The tasks skill creates ordered tasks per user story.
Say to your agentManager: Run the plan skill and then the tasks skill for this feature.
A read-only check for requirements without tasks, tasks without requirements and contradictions, posted as a comment on the Feature.
Say to your agentManager: Run the analyze skill on this feature and show me the findings.
After a clean analysis, the implement skill works the tasks story by story and moves the Feature to Done once it meets its spec.
Say to your agentManager: Run the implement skill for this feature.
A project created from the Governed Spec template starts with these work item types and statuses. You can adapt all of them to your team later.
A feature taken from spec to implementation, bound by the constitution.
A unit of work grouped by user story.
These skills come with the template in Manager:
constitutionSets the non-negotiable principles, on the wiki or project description.
specifyCreates a Feature with prioritized user stories and requirements.
clarifyResolves ambiguities with you before planning, tracked with Needs-Clarify.
planWrites the technical plan, including a constitution check.
tasksCreates ordered tasks per user story, labeling parallel ones [P].
analyzeRead-only check of spec, plan, tasks and constitution before implementing.
implementWorks the tasks story by story after a clean analysis.
The skills keep the order; you can still move a Feature by hand. A Feature labeled Needs-Clarify or Constitution-Violation is not ready to implement.
Artifacts live on work items and wiki pages, not repository files. Clarify and Analyze are fixed steps.
Pick it when many people or agents must meet the same standards. For existing code, Change-Driven is lighter; Spec-Driven fits releases, Test-Driven test-first work.
The constitution, every spec and every finding sit where your team can review them.
Get early access