Set up the doc-everything plugin for the current project — detect the source layout, scaffold the docs/features/ directory with an index, and (only if the defaults don't fit) write a .claude/doc-everything.json config so the docs-sync Stop hook watches the right paths. Use once per repo when adopting the plugin, or…
How to write/update the PRODUCT documentation for a feature — the user-facing view. Use whenever you finish or change a feature and need to record what it does for the user, or when the docs-sync Stop hook reminds you that source changed but docs didn't. Produces docs/features/ /product.md (what it is + who it's for…
How to write/update the TECHNICAL documentation for a feature — the engineering view. Use whenever you finish or change a feature implementation and need to record how it works under the hood, or when the docs-sync Stop hook reminds you that source changed but docs didn't. Produces docs/features/ /technical.md…