Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
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.
npx claudepluginhub serpro69/claude-toolbox --plugin kkHow 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).
Creates Architecture Decision Records (ADRs) and documentation for architectural decisions, API changes, features, and codebase context that future engineers need.
Documents features, APIs, architecture, and operations at appropriate decision levels. Keeps docs updated alongside code.
Generates or updates documentation for code, APIs, or systems including READMEs, API references, inline comments, technical guides, and ADRs.
Share bugs, ideas, or general feedback.
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.