write-spec
/write-spec
Write a feature design spec with numbered acceptance criteria before any plan or code. Use when starting any feature, or when a request is too vague to build without guessing.
- Author
- Zeeshan138063 ↗
- Repository
- spec-driven-kit ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Write a feature design spec with numbered acceptance criteria before any plan or code. Use when starting any feature, or when a request is too vague to build without guessing.
Original author description
Write a feature design spec with numbered acceptance criteria before any plan or code. Use when starting any feature, or when a request is too vague to build without guessing.
How it works
- Steps
- Checks before you finish
SKILL.md preview
--- name: write-spec description: Write a feature design spec with numbered acceptance criteria before any plan or code. Use when starting any feature, or when a request is too vague to build without guessing. --- # Write a feature spec A spec says **what and why**, never how. It is the yardstick every task, test and review points at. ## Steps 1. **Read first:** the ticket, the REQ it implements in `docs/prd/`, related DECs in `docs/plan/`, the principles, any ADR touching this area, open questions in `docs/questions/`, and any term in `docs/definitions/`. Use the terms exactly as defined. 2. **Copy** `docs/specs/_TEMPLATE-design.md` to `docs/specs/YYYY-MM-DD-<feature>-design.md`. 3. **Write Why** in two or three sentences, as the user sees the problem today. 4. **Write acceptance criteria** `AC-1`, `AC-2`, ... Each one testable: a test, a command output or a screenshot could prove it. "Fast" or "nice" is not a criterion. 5. **Write Non-goals.** What a reasonable person might expect that this will not do. 6. **The contract change** in words: endpoints and fields, and which roles see which field. 7. **List what is unknown.** Ask the person each question now. Write the answers into the spec, not the chat. A question nobody here can answer becomes an `OQ` (use the `open-question` skill). 8. **Stop.** Show the spec and wait for approval before planning. ## Checks before you finish - Every AC is testable and has an ID. - No technology choices in the spec. - Every term matches `docs/definitions/`. - Every decision in it either cites a DEC or ADR, or is listed as needing one.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · Zeeshan138063/spec-driven-kit | 90 | MIT |
| anhle9x/ai-worker | 100 | MIT |
| PranamRDoshi/dotclaude | 100 | MIT |
| allemaar/open-skills | 100 | Apache-2.0 |
| dzhng/skills | 100 | MIT |
| zanderadam/engy | 100 | MIT |
| tojim00d/Orbit-skills | 100 | MIT |
| trihuynh-agilityio/workez | 100 | MIT |
| me2resh/apexyard | 100 | MIT |
Database snapshot: 13.11.2026 · package version 0791bb263a36 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100v-spec
Write the spec and plan for one piece of work in a v-start project (specs/N-name/spec.md and plan.md), grounded in the real source, with a belief, a pass mark and numbered acceptance criteria, then stop for approval. Use when the user says "/v-spec", "write a spec", "spec this",… - 100pm-write-spec
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec. - 100trove-spec
Product spec writing skill. Generates structured feature specifications with user stories, acceptance criteria, and technical considerations. Use when: product spec; feature spec; write a spec. - 90Spec
Writes a grounded spec: recalls prior decisions from LTM, explores the affected code, then writes testable acceptance criteria to specs/<feature>.md. Use when the user asks to 'spec this', 'write a spec', 'define what to build', or 'write requirements / acceptance criteria'… - 100spec
Interview the user about a feature or project, then write a spec they can build from. Use when the user wants to plan, scope or spec something before coding, or runs /spec with an idea. - 95memstack-product-feature-spec
Use this skill when the user says 'feature spec', 'spec this feature', 'write a spec', 'functional requirements', or needs a detailed specification for one feature with user flows, edge cases, API definitions, and acceptance criteria. Do NOT use for full PRDs or user story generation.