Cursor rule

1---
2description: "Spec-driven development: spec templates, acceptance criteria, definition of done, pattern references, and demo scripts."
3globs: "specs/**/*.md,specs_templates/**/*.md"
4alwaysApply: false
5---
6 
7# Spec Creation Rules
8 
9These rules apply when creating or editing implementation specs. Every spec drives implementation -- incomplete specs block all downstream work.
10 
11## Stop-the-Line: Spec Quality Gate
12 
13Every spec MUST include:
14 
151. **Acceptance Criteria** -- Testable pass/fail conditions
162. **Pattern References** -- Pointers to `patterns_library/` for execution agents
173. **Success Validation Command** -- A runnable command to verify the feature works
184. **Demo Script** -- Step-by-step reproduction for QAS
19 
20If any of these are missing, the spec is not ready for implementation.
21 
22## Spec Template
23 
24Use this structure for all implementation specs:
25 
26```markdown
27# SPEC-{{TICKET_PREFIX}}-{number}: {Feature Name}
28 
29## Summary
30{One paragraph describing the feature}
31 
32## User Story
33As a [user type], I want [goal] so that [benefit].
34 
35## Acceptance Criteria
36- [ ] {Testable criterion 1}
37- [ ] {Testable criterion 2}
38- [ ] {Testable criterion 3}
39 
40## Pattern References
41- **API**: `patterns_library/api/{pattern}.md`
42- **Database**: `patterns_library/database/{pattern}.md`
43- **Security**: `docs/database/RLS_IMPLEMENTATION_GUIDE.md`
44 
45## Success Validation Command
46{runnable command to verify the feature}
47 
48## Demo Script
491. Navigate to {page}
502. Perform {action}
513. Observe {expected behavior}
524. Verify {success indicator}
53 
54## Logical Commits
551. `feat(scope): implement data model [{{TICKET_PREFIX}}-{number}]`
562. `feat(scope): add API endpoint [{{TICKET_PREFIX}}-{number}]`
573. `test(scope): add tests [{{TICKET_PREFIX}}-{number}]`
58```
59 
60## Acceptance Criteria Patterns
61 
62### User Action Criteria
63 
64```markdown
65- [ ] User can {action} -> {result}
66- [ ] When user {triggers}, system {responds}
67- [ ] User receives {feedback} after {action}
68```
69 
70### Data Criteria
71 
72```markdown
73- [ ] Data persists after {action}
74- [ ] User can only see their own {data type}
75- [ ] {field} validates {constraint}
76```
77 
78### Error Criteria
79 
80```markdown
81- [ ] Invalid input shows {error message}
82- [ ] Network failure shows retry option
83- [ ] Unauthorized access returns 401
84```
85 
86## FORBIDDEN Patterns
87 
88- Specs without testable acceptance criteria
89- Specs without pattern references (execution agents need pointers)
90- Specs with "looks good to reviewer" as done criteria (not testable)
91- Specs that skip the success validation command
92 
93## Quality Checklist
94 
95Before submitting a spec:
96 
97- [ ] All acceptance criteria are testable (verifiable pass/fail)
98- [ ] Pattern references point to existing patterns in `patterns_library/`
99- [ ] Success validation command is runnable
100- [ ] Demo script is step-by-step reproducible
101- [ ] Logical commits follow SAFe format
102- [ ] Linear ticket referenced
103 
104## Key References
105 
106- **Spec templates**: `specs_templates/`
107- **Pattern library**: `patterns_library/README.md`
108- **SAFe workflow**: `CONTRIBUTING.md`
109- **Full skill docs**: `.claude/skills/spec-creation/SKILL.md`
110