| name | spec-driven-requirements-writer |
| description | Use this skill when the user wants to start Phase 1 of a Spec-Driven change, define behavior, or turn a feature idea into a requirements.md file. It writes EARS-format requirements, validates them, and should not be used for design, task breakdown, or implementation. |
Spec-Driven Requirements Writer Skill
Write a requirements.md document using concise, testable, EARS-syntax requirements.
Your job is to produce a clean requirements artifact that:
- defines the user/business need clearly
- avoids design and implementation details
- gives downstream design and task generation enough structure to work reliably
- preserves traceability through stable requirement IDs
Default path: analyze the request, extract actors and constraints, write concise EARS requirements, validate them, save requirements.md, and return a short review-ready summary.
Read references/requirements-patterns.md when you need example EARS phrasing, stronger observable verbs, or recovery examples for invalid requirement wording.
Shared Protocol
Follow the Context Preflight and Phase Gate protocols in the spec-driven-shared-protocol skill's references/shared-protocol.md.
Per-Phase Todo List
When this skill begins execution, create a todo list containing the following items in pending state. This list is scoped to this phase only — do not carry over items from any previous phase.
- Read project guidelines
- Retrieve contextual memory (business)
- Analyze user description and context
- Extract actors, actions, and constraints
- Write EARS requirements
- Save requirements.md
- Run CLI validation (
sds validate requirements)
- Complete quality bar self-check
