write-speclisted
Install: claude install-skill ValentinNikolaev/agent-skills
# Write a Specification
Draft a compact, implementable contract before a significant change. Adapted from Addy Osmani's `spec-driven-development` workflow; see the bundled license and repository third-party notice.
## Route precisely
- Use when the user requests a specification, PRD, or explicit requirements for a proposed feature or substantial change.
- Use `review-spec` to judge an existing draft, `api-and-interface-design` when the primary deliverable is one interface contract, `planning-and-task-breakdown` to order implementation work, and `verify-impl` to compare finished code with authoritative requirements.
- Do not require a specification for a mechanical edit. Do not start implementation merely because the spec is written.
## Establish authority and scope
Read the user's requested outcome, repository instructions, related contracts, existing behavior, and any binding decision records. Separate confirmed facts from proposed behavior and assumptions. Ask only for information that determines a material product or safety choice; otherwise make a clearly labeled draft assumption.
## Draft the contract
1. State the problem, intended users or consumers, objective, and scope. Identify what behavior is explicitly excluded when that prevents ambiguity.
2. Break a broad requirement into independently testable capabilities. For each, describe inputs, outputs, state changes, defaults, failure behavior, and the owner of the data or side effect where relevant.
3. Specify pu