name: sparc-specification-best-practices description: 'Sub-skill of sparc-specification: Best Practices.' version: 1.0.0 category: development type: reference scripts_exempt: true
Best Practices
Best Practices
- Be Specific: Avoid ambiguous terms like "fast" or "user-friendly"
- Make it Testable: Each requirement should have clear pass/fail criteria
- Consider Edge Cases: What happens when things go wrong?
- Think End-to-End: Consider the full user journey
- Version Control: Track specification changes
- Get Feedback: Validate with stakeholders early