Keeps documentation in sync with code changes and project state. Triggers: "update documentation", "patch the docs", "sync docs with code changes", "update architecture docs".
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
Keeps documentation in sync with code changes and project state. Triggers: "update documentation", "patch the docs", "sync docs with code changes", "update architecture docs".
version
3
tier
protocol
Keeps documentation in sync with code changes and project state.
Scope: Understand the [Trigger] (e.g., "We refactored the Audio Graph").
Goal: The mission is Truth Convergence. Make the map match the territory.
Value: Outdated docs are debt. They mislead devs and waste hours. You are the cleaner.
New Features: If this is a New Feature, you must define its "Home". Does it need a new concepts/X.md? or a section in features/Y.md? Do not leave it homeless.
Mode Selection (§CMD_SELECT_MODE):
On selection: Read the corresponding modes/{mode}.md file. It defines Role, Goal, Mindset, and Operation Strategy.
On "Custom": Read ALL 3 named mode files first (modes/surgical.md, modes/refine.md, modes/audit.md), then accept user's framing. Parse into role/goal/mindset.
Record: Store the selected mode. It configures:
Phase 0 role (from mode file)
Phase 1 diagnosis strategy (from mode file)
Phase 2 operation approach (from mode file)
Interrogation Topics (Documentation)
Brief pre-flight interrogation before context loading. Adapt to the task -- skip irrelevant topics, invent new ones as needed.
Standard topics (typically covered once):
Scope & boundaries -- which docs are in/out, depth of changes, new vs update
Audience & tone -- who reads these docs, technical level, formality
Source of truth -- where does the "correct" information live (code, specs, conversations)
Freshness assessment -- how stale are the current docs, when were they last updated
Structure & format -- should we restructure, add diagrams, change headings
Dependencies -- do changes to one doc require cascading updates to others
New feature docs -- does this need a new file, a new section, or a new concept page
Risks & constraints -- what could go wrong with doc changes (broken links, stale references)
Repeatable topics (can be selected any number of times):
Followup -- Clarify or revisit answers from previous rounds
Devil's advocate -- Challenge assumptions about doc changes
Deep dive -- Drill into a specific doc area in detail
1. Diagnosis & Planning
Before cutting, understand the anatomy and draft the procedure.
Survey: Use targeted reads to identify outdated sections.
Plan: Be specific. "Rewrite Section 3 of X.md" is better than "Update X.md".
Walk-through (optional):
§CMD_WALK_THROUGH_RESULTS Configuration:
mode: "plan"
gateQuestion: "Surgical plan ready. Walk through the operations before cutting?"
debriefFile: "DOCUMENTATION_PLAN.md"
templateFile: "assets/TEMPLATE_DOCUMENTATION_PLAN.md"
planQuestions:
- "Is this the right scope for this operation?"
- "Any docs I'm missing that should also be updated?"
- "Concerns about this change breaking existing references?"
If any items are flagged for revision, return to the plan for edits before proceeding.
On "Other" (free-text) at phase transition: The user is describing new requirements. Route to Phase 0 (Setup) to scope it before operating -- do NOT stay in Phase 2.A or jump to synthesis.
2.B. Agent Handoff
Hand off to a single autonomous agent.
§CMD_EXECUTE_PHASE_STEPS(2.B.*)
§CMD_HANDOFF_TO_AGENT with:
{"agentName":"writer","startAtPhase":"2.A: Operation","planOrDirective":"[sessionDir]/DOCUMENTATION_PLAN.md","logFile":"DOCUMENTATION_LOG.md","taskSummary":"Execute the document update plan: [brief description from taskSummary]"}
2.C. Parallel Agent Handoff
Hand off to multiple autonomous agents in parallel.
§CMD_EXECUTE_PHASE_STEPS(2.C.*)
§CMD_PARALLEL_HANDOFF with the plan from DOCUMENTATION_PLAN.md.
Collects all documentation files created, modified, or deleted during this session.
Presents multichoice for TOC.md additions, description updates, and stale entry removals.
Auto-applies selected changes to docs/TOC.md.
Skips silently if no documentation files were touched.
Walk-through config:
§CMD_WALK_THROUGH_RESULTS Configuration:
mode: "results"
gateQuestion: "Documentation complete. Walk through the updates?"
debriefFile: "DOCUMENTATION.md"
templateFile: "assets/TEMPLATE_DOCUMENTATION.md"
