From kk
Guides documentation after feature implementation or bug fixes: search knowledge base for conventions, update ARCHITECTURE.md and TESTING.md, write ADRs for decisions.
How this skill is triggered — by the user, by Claude, or both
Slash command
/kk:documentation-processThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
For capy knowledge base conventions, see [capy-knowledge-protocol.md](../_shared/capy-knowledge-protocol.md).
For capy knowledge base conventions, see capy-knowledge-protocol.md.
Capy search: Before writing docs, search kk:arch-decisions and kk:project-conventions for decisions that should be reflected in documentation — decisions not obvious from code alone.
/docs/contributing/ARCHITECTURE.md and Test documentation in /docs/contributing/TESTING.md for other developers, so anyone could easily pick up the work and understand the project and the feature that was added./docs/adr for any non-trivial/non-obvious decisions that should be preserved.npx claudepluginhub serpro69/claude-toolbox --plugin kkDocuments architectural decisions, API changes, and project context using ADRs, inline comments, and changelogs. Helps capture why decisions were made for future engineers and agents.
Creates Architecture Decision Records (ADRs) and documentation for architectural decisions, API changes, features, and codebase context that future engineers need.
Records architectural decisions and documentation context. Use when making significant technical choices, changing APIs, or shipping features that need rationale captured for future engineers.