rules-orchestrationlisted

## Routing Guidance - IMMEDIATELY after significant skill execution (plan-lifecycle, refine) when conventions were established. - FIRST when CLAUDE.md exceeds 200 lines or .claude/rules/ has more than 10 files. - Do NOT use for one-off questions or temporary instructions. - Do NOT modify managed/enterprise rules at system paths. ## CONTRAST - NOT for: capturing session learnings to scratchpad — use refine MEMORIZE - NOT for: archiving completed plans — use project-maintenance PLAN-ARCHIVE - NOT for: one-off temp instructions that won't be repeated ## Decision Router IF user wants to extract insights from current/last conversation → **ANALYZE** mode IF user wants to restructure or audit existing rules → **RESTRUCTURE** mode IF user wants to add a specific convention to rules → **ADD** mode IF user wants to review and approve pending proposals → **REVIEW** mode IF user wants to sync with recent skill execution or learn output → **SYNC** mode IF user wants to find rule conflicts across hierarchy → **AUDIT** mode IF target is ambiguous → ask: "Analyze current conversation, restructure existing rules, add a specific convention, review pending proposals, sync with recent work, or audit for conflicts?" --- ## ANALYZE Mode Extracts insights from conversation history or skill output and synthesizes them into structured rule proposals. ### When After conversation or skill execution with discoverable conventions, anti-patterns, or decisions worth codifying. ### Process 1. **C