Escrita e Conteúdo

Creates backend docs (api_spec.md, database_schema.md). Use when project has backend API or database.

Creates complete project documentation system (project docs, reference, tasks, tests). Use when bootstrapping docs from scratch or regenerating all.

Creates core project docs (requirements, architecture, tech stack, patterns catalog). Use for any project regardless of type.

Creates task management docs (kanban board, workflow rules) with configured tracker integration. Use when setting up task tracking for a project.

Use when an evaluation run needs review-driven documentation updates and a structured documentation summary.

Extracts procedural content from project docs into slash commands. Use when docs contain deploy, test, or troubleshoot procedures.

Checks races, deadlocks, async hazards, TOCTOU, blocking I/O, and shared resource contention. Use when auditing concurrency correctness.

Checks inline code documentation quality: WHY-not-WHAT, density, forbidden content, docstrings quality, actuality, legacy cleanup. Use when auditing comments and docstrings.

Coordinates project documentation creation with single context gathering and project type detection. Use when generating project docs subset.

Checks hierarchy, links, SSOT, compression, requirements compliance, freshness, legacy cleanup. Use when auditing documentation structure.

Creates test documentation (testing-strategy.md, tests/README.md) with Risk-Based Testing philosophy. Use when setting up test strategy for a project.

Creates root documentation files (AGENTS.md, CLAUDE.md, docs/README.md, standards, principles). Use for initial project doc setup.