write-documentlisted
Install: claude install-skill BhangeeF16/kaizen
# Write Document
Produce or update exactly one properly-shaped Knowledge Object. Every `doctype` is either graph-mapped (one of the fifteen node types in [Graph Node Schema](../../templates/graph-schema.md)) or non-graph (stays a plain prose file). Which one it is decides how this skill writes it — see below — but both apply the same formatting law from `documentation-standards` for whichever fields/sections remain.
## Dispatch
One synchronous `Agent`-tool call. `subagent_type` is whatever role the dispatching action entry names (`business-analyst` for `promote_to_product_knowledge`, `documentation-steward` for `documentation_update`, `solution-architect` for the ADR half of `technical_design`) — this skill defines the contract, not the persona.
## Graph-mapped doctypes: route through `kaizen graph new`/`update`
For these `doctype` values, never hand-write the file or its front matter directly — call the CLI, which allocates the id, serializes front matter, and writes the file:
| `doctype` | node type | CLI verb |
| --- | --- | --- |
| `business-rule` | `BR` | `kaizen graph new business-rule` |
| `requirement` | `FR` | `kaizen graph new requirement` |
| `nfr` | `NFR` | `kaizen graph new nfr` |
| `adr` | `ADR` | `kaizen graph new adr` |
| `user-story` | `US` | `kaizen graph new user-story` |
| `question` | `QST` | `kaizen graph new question` |
| `acceptance-criteria` | `AC` | `kaizen graph new acceptance-criteria` |
| `user-flow` | `FLOW` | `kaizen graph new user-flow` |