← ClaudeAtlas

write-build-doclisted

Turns rough notes - a goal, a loose checklist, and implementation options or components - into a concise Markdown build document a coding agent can follow, saved as docs/woz-docs/spec-dev/<slug>/BUILD.md. Use when asked to write, generate, or draft a build doc, build plan, or build spec, or to turn notes, requirements, a SPEC.md, or architectural options into something a coding agent can implement. Not for PRDs or specs (use write-spec), for multi-agent execution plans (use orchestrate-subagents), for writing a prompt (use optimize-prompt), or for general documentation.
woznet/wozdev · ★ 0 · Web & Frontend · score 72
Install: claude install-skill woznet/wozdev
# Write Build Doc Turn unstructured notes into a build document that states what to build and how, in a fixed structure a coding agent can follow without asking. **Reader:** an autonomous coding agent first, a human reviewer second. Every line must tell one of them what to do or how to know it is done; cut anything else. ## Input Notes in the chat, a file path the user names, or both. They may hold a goal, task lists, alternative approaches, components, constraints, and rationale in any order. A `SPEC.md` from `write-spec` is valid input: its folder supplies the slug, and its requirement IDs, such as `(FR2)`, go on the Done When lines that prove them. ## Output - **Path:** `docs/woz-docs/spec-dev/<slug>/BUILD.md`, relative to the repository root. Create the folder if needed. Write the file with the file-write tool, not a shell heredoc. - **Slug:** kebab-case, 2-4 words, subject noun first (`version-bump-ci`, `rumdl-installer`). When the input is a `SPEC.md` under `docs/woz-docs/spec-dev/<slug>/`, reuse that slug and write `BUILD.md` beside it. Otherwise, if `<slug>/BUILD.md` exists, use `<slug>-2`, `-3`. Update an existing `BUILD.md` in place only when the user asks for that doc to change. - **Format:** exactly the structure in `references/build-doc-template.md`. - **Chat reply:** the file path, plus each Open Question if there are any. No summary of the doc. **Host plan mode:** if the host restricts writes to its own plan file, put the build doc there, and write `docs