with one click
team-init-docs
Initialize comprehensive documentation for the codebase
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Initialize comprehensive documentation for the codebase
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Build and deploy features — branch, implement, commit, review, test, deploy, PR/merge
shadcn/ui component patterns including Radix UI primitives, CVA variants, form components with React Hook Form, and Tailwind CSS styling. Use when creating UI components, building forms, implementing design systems, or working with shadcn/ui.
Add critical test coverage — tests ONLY for functionality that could cause production disasters
List all available tools with their signatures and purposes
Analyze Claude Code audit logs — session summaries, metrics, timelines, anomaly detection, and claim verification
Technical debt and refactoring — analyze, refactor, and validate code improvements
| name | team-init-docs |
| description | Initialize comprehensive documentation for the codebase |
| argument-hint | [optional: specific area to document] |
| disable-model-invocation | true |
| allowed-tools | TaskCreate, TaskUpdate, TaskList, TaskGet |
Create comprehensive, well-organized documentation for the codebase.
Target area: $ARGUMENTS
Enable with CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1
Create a team and spawn teammates:
init-docsCreate the following task list:
| # | Task | Owner | Blocked By |
|---|---|---|---|
| 1 | Analyze codebase structure, frameworks, and architecture | documentor | — |
| 2 | Create docs/ directory structure and generate documentation | documentor | 1 |
| 3 | Build table of contents and cross-link all documents | documentor | 2 |
Execute using the Task tool:
Task(documentor, "Initialize comprehensive documentation for the codebase. Focus area: $ARGUMENTS. Analyze project structure, create docs/ folder hierarchy, generate documentation for all major modules, and build a table of contents with cross-links.")After completion, the docs/ folder should contain:
docs/README.md — main table of contentsdocs/architecture/ — system design documentationdocs/api/ — API documentation (if applicable)docs/guides/ — how-to guidesdocs/reference/ — configuration and reference material