34 lines
1.1 KiB
Markdown
34 lines
1.1 KiB
Markdown
|
# Specification Quality Checklist: [FEATURE NAME]
|
||
|
|
|
||
|
|
**Purpose**: Validate specification completeness and quality before proceeding to planning
|
||
|
|
**Created**: [DATE]
|
||
|
|
**Feature**: [Link to spec.md]
|
||
|
|
|
||
|
|
## Content Quality
|
||
|
|
|
||
|
|
- [ ] No implementation details (languages, frameworks, APIs)
|
||
|
|
- [ ] Focused on user value and business needs
|
||
|
|
- [ ] Written for non-technical stakeholders
|
||
|
|
- [ ] All mandatory sections completed
|
||
|
|
|
||
|
|
## Requirement Completeness
|
||
|
|
|
||
|
|
- [ ] No [NEEDS CLARIFICATION] markers remain
|
||
|
|
- [ ] Requirements are testable and unambiguous
|
||
|
|
- [ ] Success criteria are measurable
|
||
|
|
- [ ] Success criteria are technology-agnostic (no implementation details)
|
||
|
|
- [ ] All acceptance scenarios are defined
|
||
|
|
- [ ] Edge cases are identified
|
||
|
|
- [ ] Scope is clearly bounded
|
||
|
|
- [ ] Dependencies and assumptions identified
|
||
|
|
|
||
|
|
## Feature Readiness
|
||
|
|
|
||
|
|
- [ ] All functional requirements have clear acceptance criteria
|
||
|
|
- [ ] User scenarios cover primary flows
|
||
|
|
- [ ] Feature meets measurable outcomes defined in Success Criteria
|
||
|
|
- [ ] No implementation details leak into specification
|
||
|
|
|
||
|
|
## Notes
|
||
|
|
|
||
|
|
- Items marked incomplete require spec updates before `/sdd:01-specify` or `/sdd:01-plan`
|