What problem does it solve? When planning changes in the mj-agent repository, it is hard to know which of the 10 canonical documentation types (Plan, SPEC, ADR, RUNBOOK, GUIDE, STANDARD, ISSUE, ASSESSMENT, CHANGELOG, INDEX) must be created or updated. This Skill analyzes the diff, Issue, or SPEC scope and produces a complete Documentation Decision matrix so nothing is missed. ## Core Features & Use Cases - Scope Analysis: Reads git diff, GitHub Issue body, and existing docs to identify documented versus missing coverage per mj-agent module, including A/B/C flavor classification. - Type & Track Evaluation: Applies Meta v2.1 type tables and ADR-014 boundary rules to assign each gap a document type and tri-track classification (code, agent, engineering-workflow, shared), with Q-05/Q-12 ambiguity prompts for mixed content. - Dependency-Ordered Task List: Outputs a 10-row §7.1 matrix plus an ordered task list that feeds directly into the mj-agent-flow-plan Stage 4 Plan body. - Use Case: Before starting a multi-module change, ask which documents are needed; the Skill returns the full decision matrix showing what to create, update, or skip, with reasons and evidence. ## Quick Start Ask the agent to evaluate what documentation is needed for the current mj-agent branch changes and produce the §7.1 Documentation Decision matrix.
