Initial commit
This commit is contained in:
85
commands/check-spec.md
Normal file
85
commands/check-spec.md
Normal file
@@ -0,0 +1,85 @@
|
||||
# Validate Specification Quality
|
||||
|
||||
## Spec File: $ARGUMENTS
|
||||
|
||||
Review a feature specification for completeness and implementation readiness.
|
||||
|
||||
## Validation Checklist
|
||||
|
||||
### Requirements Clarity
|
||||
|
||||
- [ ] Feature purpose and goals clearly defined
|
||||
- [ ] Target users and use cases identified
|
||||
- [ ] Success criteria measurable and specific
|
||||
- [ ] Core functionality well-described
|
||||
|
||||
### User Experience
|
||||
|
||||
- [ ] User stories cover main workflows
|
||||
- [ ] Edge cases and error states considered
|
||||
- [ ] User interface requirements specified
|
||||
- [ ] Accessibility considerations included
|
||||
|
||||
### Technical Specifications
|
||||
|
||||
- [ ] Data requirements clearly defined
|
||||
- [ ] Integration points with existing systems identified
|
||||
- [ ] Performance and scalability requirements specified
|
||||
- [ ] Security and authentication needs addressed
|
||||
|
||||
### Implementation Readiness
|
||||
|
||||
- [ ] Acceptance criteria are testable
|
||||
- [ ] Technical constraints documented
|
||||
- [ ] Dependencies and external services noted
|
||||
- [ ] Out-of-scope items clearly defined
|
||||
|
||||
### Project Management
|
||||
|
||||
- [ ] MVP vs future enhancements distinguished
|
||||
- [ ] Relative priority/importance indicated
|
||||
- [ ] Potential risks or challenges flagged
|
||||
- [ ] Scope is reasonable for single implementation
|
||||
|
||||
## Analysis Process
|
||||
|
||||
1. **Completeness Check**
|
||||
- Scan for missing critical sections
|
||||
- Identify vague or ambiguous requirements
|
||||
- Flag areas needing more detail
|
||||
|
||||
2. **Feasibility Assessment**
|
||||
- Check against existing codebase patterns
|
||||
- Identify potential technical challenges
|
||||
- Estimate implementation complexity
|
||||
|
||||
3. **Quality Review**
|
||||
- Ensure requirements are specific and measurable
|
||||
- Verify user stories follow good practices
|
||||
- Check that acceptance criteria are testable
|
||||
|
||||
## Output
|
||||
|
||||
### Quality Score (1-10)
|
||||
|
||||
Rate the specification's readiness for implementation:
|
||||
|
||||
- **1-3**: Major gaps, needs significant work
|
||||
- **4-6**: Good foundation, some areas need clarification
|
||||
- **7-8**: Well-defined, minor improvements possible
|
||||
- **9-10**: Comprehensive and implementation-ready
|
||||
|
||||
### Feedback Report
|
||||
|
||||
- **Strengths**: What the spec does well
|
||||
- **Missing Elements**: Critical gaps to address
|
||||
- **Clarification Needed**: Vague or ambiguous areas
|
||||
- **Suggestions**: Ways to improve the specification
|
||||
- **Risk Assessment**: Potential implementation challenges
|
||||
|
||||
### Recommended Actions
|
||||
|
||||
- **Ready to implement**: Proceed with `/execute-spec`
|
||||
- **Needs revision**: Specific areas to improve first
|
||||
- **Requires research**: External factors to investigate
|
||||
- **Scope adjustment**: Recommendations for MVP vs full feature
|
||||
Reference in New Issue
Block a user