spec-creation
Spec creation with pattern references, acceptance criteria, and demo scripts. Use when creating implementation specs, defining acceptance criteria, or breaking down user stories.
When & Why to Use This Skill
The Spec Creation skill is a specialized tool designed to bridge the gap between business requirements and technical execution. It standardizes the creation of implementation specifications by enforcing the inclusion of testable acceptance criteria, architectural pattern references, and automated validation commands. By providing a rigorous template and 'stop-the-line' quality checks, it ensures that developers and AI agents have a clear, unambiguous roadmap for building and verifying features, significantly reducing technical debt and communication overhead.
Use Cases
- Translating high-level business requirements and user stories into detailed, actionable technical specifications.
- Defining clear, testable acceptance criteria to ensure feature completion aligns with stakeholder expectations.
- Standardizing development workflows by providing explicit pattern references for UI, API, and security implementations.
- Generating automated success validation commands and manual demo scripts to streamline the QA and verification process.
- Organizing complex feature builds into logical commit sequences to maintain a clean and traceable version control history.
| name | spec-creation |
|---|---|
| description | Spec creation with pattern references, acceptance criteria, and demo scripts. Use when creating implementation specs, defining acceptance criteria, or breaking down user stories. |
Spec Creation Skill
Purpose
Guide spec creation with clear acceptance criteria, pattern references for execution agents, and testable success validation commands.
When This Skill Applies
Invoke this skill when:
- Creating implementation specs
- Breaking down user stories
- Defining acceptance criteria
- Adding pattern references for execution
- Creating demo scripts for validation
- Translating business requirements to technical specs
Stop-the-Line Conditions
FORBIDDEN Patterns
# FORBIDDEN: Missing acceptance criteria
## Implementation
Just do the thing.
<!-- No testable outcomes defined -->
# FORBIDDEN: No pattern reference
## Technical Approach
Build it however you want.
<!-- Execution agents need pattern pointers -->
# FORBIDDEN: No success validation
## Done Criteria
Looks good to reviewer.
<!-- No command to verify completion -->
CORRECT Patterns
# CORRECT: Clear acceptance criteria
## Acceptance Criteria
- [ ] User can click button → modal appears
- [ ] Modal shows validation errors for empty fields
- [ ] Successful submission shows success toast
# CORRECT: Pattern reference for execution
## Pattern Reference
- **UI Pattern**: `docs/patterns/ui/modal-form.md`
- **API Pattern**: `docs/patterns/api/crud-endpoint.md`
- **RLS Pattern**: `docs/patterns/security/rls-user-data.md`
# CORRECT: Success validation command
## Success Validation
```bash
# Run these commands to verify implementation
yarn test:unit --grep "ModalForm"
curl -X POST http://localhost:3000/api/endpoint -d '{"test": true}'
```
## Spec Template (MANDATORY)
Every spec must include:
````markdown
# SPEC-{TICKET_PREFIX}-{number}: {Feature Name}
## Summary
{One paragraph describing the feature}
## User Story
As a [user type], I want [goal] so that [benefit].
## Acceptance Criteria
- [ ] {Testable criterion 1}
- [ ] {Testable criterion 2}
- [ ] {Testable criterion 3}
## Pattern References
- **UI**: `docs/patterns/ui/{pattern}.md`
- **API**: `docs/patterns/api/{pattern}.md`
- **Database**: `docs/patterns/database/{pattern}.md`
- **Security**: Follow RLS patterns in `docs/database/RLS_IMPLEMENTATION_GUIDE.md`
## Success Validation Command
```bash
# Run this to verify the feature works
{validation command}
Demo Script
- Navigate to {page}
- Click {button}
- Observe {expected behavior}
- Verify {success indicator}
Logical Commits
feat(scope): implement data model [{TICKET_PREFIX}-{number}]feat(scope): add API endpoint [{TICKET_PREFIX}-{number}]feat(scope): create UI component [{TICKET_PREFIX}-{number}]test(scope): add unit tests [{TICKET_PREFIX}-{number}]
## Acceptance Criteria Patterns
### User Action Criteria
```markdown
- [ ] User can {action} → {result}
- [ ] When user {triggers}, system {responds}
- [ ] User receives {feedback} after {action}
```
### Data Criteria
```markdown
- [ ] Data persists after {action}
- [ ] User can only see their own {data type}
- [ ] {field} validates {constraint}
```
### Error Criteria
```markdown
- [ ] Invalid input shows {error message}
- [ ] Network failure shows retry option
- [ ] Unauthorized access returns 401
```
## Pattern Discovery for Specs
Before writing any spec:
```bash
# Find existing patterns
ls docs/patterns/
# Search for similar implementations
grep -r "similar feature" app/ lib/
# Check existing specs for format
ls specs/
cat specs/SPEC-{TICKET_PREFIX}-XXX-example.md
```
## Spec Quality Checklist
Before submitting spec:
- [ ] All acceptance criteria are testable (can verify pass/fail)
- [ ] Pattern references point to existing patterns
- [ ] Success validation command is runnable
- [ ] Demo script is step-by-step reproducible
- [ ] Logical commits follow SAFe format
- [ ] Linear ticket referenced
## Output Locations
| Output Type | Location |
| ------------ | ----------------------------------------------------- |
| Impl specs | `specs/SPEC-{TICKET_PREFIX}-{number}-{description}.md` |
| Requirements | `docs/agent-outputs/requirements/{TICKET_PREFIX}-{number}-*.md` |
| ADRs | `docs/adr/ADR-{number}-{description}.md` |
## Evidence for Linear
After spec approval:
```markdown
**BSA Spec Evidence**
**Spec**: specs/SPEC-{TICKET_PREFIX}-{number}-{description}.md
**Status**: Approved by [reviewer]
**Deliverables**:
- [x] Acceptance criteria defined
- [x] Pattern references added
- [x] Demo script created
- [x] Ready for implementation
```
## Authoritative References
- **Spec Template**: `docs/archive/specs/spec_template.md`
- **Pattern Library**: `docs/patterns/README.md`
- **Planning Guide**: `docs/team/PLANNING-AGENT-META-PROMPT.md`
- **SAFe Workflow**: `CONTRIBUTING.md`