tessl-labs/spec-driven-development
Spec-driven workflow covering requirement gathering, spec authoring, implementation review, and verification — with skills, rules, and evaluation scenarios.
96
1.19x
Quality
90%
Does it follow best practices?
Impact
98%
1.19xAverage score across 9 eval scenarios
Securityby
Passed
No known issues
spec-styleguide.mddocs/
Spec Styleguide
Best Practices
- Provide context: Add markdown text around test links explaining what should be checked
- Use headings: Organize related requirements under clear headings
- Be specific: Describe expected behavior, edge cases, and constraints
- Granular tests: Place
[@test]links next to the requirements they verify. Create targeted test files for separate requirements. - Keep specs synchronized: Ensure specs stay up-to-date with implementation