Update Docs

Trigger

• Keywords: update docs, sync docs, docs out of date, update-docs

When NOT to Use

• Document review (use /codex-review-doc)
• Creating new docs (use /tech-spec or /create-request)
• Document refactoring (use /doc-refactor)

Auto-Trigger

Auto-triggered after precommit Pass, only when the change maps to a feature under docs/features/ (see @rules/auto-loop.md Doc Sync Note). Can also be invoked manually.

Task

Step 1: Locate Docs and Related Code (5-Level Cascade)

Key principle: can't find target → ## Gate: ⚠️ Need Human — don't guess or create new docs.

Use the shared feature context resolution algorithm (see @skills/tech-spec/references/feature-context-resolution.md):

Step 2: Research Current Code State

Key research items:

• Any new scripts / skills / commands added?
• Any modified logic in existing files?
• Any new configuration or rules added?
• Any API or interface changes?

Step 3: Compare Docs vs Code Differences

Step 4: Update Docs

Update document content based on differences:

1. Architecture diagrams (Mermaid sequenceDiagram / flowchart)
2. Core service table
3. API description
4. Data model

Step 5: Verification

After update:

1. Re-read updated document sections
2. Verify all new modules are documented
3. Verify all removed modules are cleaned up

Safety Valve

After doc sync, compare code diff against pre-sync baseline. If new code changes exist (e.g., lint:fix modified code), return to review loop.

Output

## Doc Update Report

| Document | Sections Updated | Status |
|----------|-----------------|--------|

## Changes Made
- <summary of each update>

## Verification
- [ ] New modules documented
- [ ] Removed modules cleaned
- [ ] Diagrams updated