kata-setup
Installation
SKILL.md
Kata Setup
Collect documentation for later review. Do not rewrite, classify, or claim to verify its content against implementation.
Inspect and select
- Resolve the requested project root; ask if unclear. Read applicable instructions, root README, existing Docs Kata rules, index, intake log, and
templates/docs-agents.mdbeside this skill. Check Git status; preserve local edits. - Inventory prose and supporting assets in project documentation locations. Search links and build configuration for consumers. Extensions and category folders do not prove documentation status or prior review.
- Preserve root entry points, policies, licenses, changelogs, and all agent instruction files and their scope. Exclude source, tests, fixtures, dependencies, generated or vendored documents, installed skills, and separate repositories. Do not follow symlinks outside the project.
- Include unprocessed category documents on first setup. On repeats, retain inbox contents and processed documents. Retain and report documents whose prior setup state is unclear.
- Retain files needed at fixed paths by builds, websites, published URLs, or package consumers unless this change preserves those uses. Log exceptions and reasons.
- Show the inventory and proposed moves. Setup authorizes routine moves; ask only about unresolved content, behavior, instruction, or path conflicts. Continue independent work.