write-speclisted
Install: claude install-skill woznet/wozdev
# Write Spec
Turn unstructured notes into two documents: a `PRD.md` that says what to build and why, and a `SPEC.md` that says how, with every requirement traced to the steps and checks that satisfy it.
**Reader:** an autonomous coding agent first, a human reviewer second. Every line must state a requirement, a decision, or a check; cut anything else.
## Input
Notes in the chat, a file path the user names, or both: goals, workflows, inputs, outputs, constraints, and rationale in any order.
## Output
- **Paths:** `docs/woz-docs/spec-dev/<slug>/PRD.md` and `docs/woz-docs/spec-dev/<slug>/SPEC.md`, relative to the repository root. Create the folders if needed. Write with the file-write tool, not a shell heredoc.
- **Slug:** kebab-case, 2-4 words, subject noun first (`version-bump-enforcer`, `subagent-batch-planner`). If the folder exists, use `<slug>-2`, `-3`. Update an existing spec in place only when the user asks for that spec to change; read both files first.
- **Format:** exactly the structures in `references/prd-template.md` and `references/spec-template.md`.
- **Chat reply:** both file paths, plus each Open Question if there are any. No summary of the documents.
**Host plan mode:** if the host restricts writes to its own plan file, draft both documents there, and write `docs/woz-docs/spec-dev/` once the host plan is approved.
## Clarification Gate
Check the notes against four pillars: **objective** (what problem is solved or artifact produced), **trigger and input