---
inclusion: fileMatch
fileMatchPattern: ["**/*.md"]
---

# Spec-Kit Specifications

- Describe user needs, outcomes, and acceptance criteria; exclude tech stack, frameworks, and architecture choices.
- Flag every ambiguity or unstated assumption explicitly with a `[NEEDS CLARIFICATION]` marker instead of inventing a plausible answer.
- Make every requirement testable and every success criterion measurable; trace each requirement back to a concrete user need.
- Include no speculative "nice-to-have" features: every capability in the spec must be backed by a concrete user story.
- Keep the spec readable: move dense implementation detail into separate linked files rather than inlining it.
- Run a completeness checklist before implementation starts: requirements complete, testable, measurable, traceable.
- Write the spec for business stakeholders: a non-developer must be able to read it and confirm it matches their intent.