spec-writer

Topics in the source

• Spec writer
• Start
• Before writing
• Writing
• Checks
• Hand-off and after
• Gotchas
• Files

A spec exists so that the coder makes no decision nobody approved. Every choice it leaves open is made by the coder alone and discovered in review, where it costs a rewrite instead of a line. So the spec carries the decisions — the seams between pieces of code, the contract, the risky inputs, what «done» is — and leaves the bodies to the coder. The session that talked with the owner writes it: half of the decisions live only in that conversation, and an agent handed the files would rebuild the other half and lose this one. A fresh agent then reads the result cold. Read the project's file .claude/spec-writer.project.md (the nearest one above the spec's path; a worktree has its own copy). It says where specs live, their language, the contract format, how to measure a query, who codes, the project's gates and extra sections. No such file → build it with the owner from project-template.md first; a spec written without it guesses exactly the project facts the coder cannot. Every question that would change the contract, the files, the split into parts or the tests is closed first — with the owner, at most five questions at a time, each with options and your recommendation. The project's

This is an excerpt. Refer to the complete source and its current requirements.