planflow-ai 1.3.0 → 1.3.4

package/.claude/commands/brainstorm.md

@@ -58,7 +58,7 @@ WHAT IT IS:
 
 WHAT IT IS NOT:
   - Not /discovery-plan — no codebase scanning, no requirements docs
-  - Not /brain — no knowledge capture, no wiki-links
+  - Not /note — no knowledge capture, no wiki-links
   - Not a plan — no phases, no complexity scores
 
 RECOMMENDED MODEL:
@@ -67,7 +67,7 @@ RECOMMENDED MODEL:
 RELATED COMMANDS:
   /discovery-plan   Ground the brainstorm idea into the project
   /create-plan      Create plan from discovery document
-  /brain            Capture knowledge (different purpose)
+  /note             Capture knowledge (different purpose)
 ```
 
 ---

package/.claude/commands/discovery-plan.md

@@ -278,6 +278,7 @@ This command uses hierarchical context loading to reduce context consumption. In
 | SKL-DIS-1 | Discovery skill workflow | Understanding full process |
 | TLS-IQ-2 | How to switch to Plan mode | Before asking questions |
 | TLS-IQ-3 | How to ask questions | When gathering requirements |
+| COR-CG-1 | Compaction guide | Load when compacting mid-discovery |
 
 ### Expansion Instructions
 
@@ -389,6 +390,16 @@ Only save if the user approves. Do not re-ask if declined.
 
 ---
 
+## Discovery Sub-Agents
+
+After reading referenced documents (Step 1), three parallel Agent sub-agents explore the codebase simultaneously: **Similar Features** (finds related existing code), **API/Data Patterns** (maps endpoints and service patterns), and **Schema/Types** (explores type definitions and schemas). All use haiku model.
+
+Each sub-agent returns condensed JSON findings (under 2K tokens) that the coordinator merges into a `## Codebase Analysis` section in the discovery document. Findings also inform the clarifying questions in Step 2.
+
+Always-on — no configuration needed. See `.claude/resources/core/discovery-sub-agents.md` for full rules.
+
+---
+
 ## Design Awareness
 
 During discovery, always ask whether the feature involves UI work. If confirmed, follow the design question flow to capture structured design tokens (colors, typography, spacing, component patterns) into a `## Design Context` section in the discovery document.

package/.claude/commands/execute-plan.md

@@ -328,11 +328,25 @@ This command uses hierarchical context loading to reduce context consumption. In
 
 | Code | Description | When to Expand |
 |------|-------------|----------------|
-| SKL-EXEC-1 | Execution workflow | Understanding full process |
-| SKL-EXEC-2 | Complexity-based grouping | Determining execution strategy |
+| SKL-EXEC-2 | Critical rules (build, DB) | Need build/DB command restrictions |
+| SKL-EXEC-4 | Analyze complexity | Determining execution strategy |
+| SKL-EXEC-6 | Execute phase with Plan mode | Running a specific phase |
+| SKL-EXEC-8 | Phase-boundary compaction | Compacting between phases |
+| SKL-EXEC-9 | Handle tests phase | Executing the tests phase |
+| SKL-EXEC-10 | Build and test verification | Final verification step |
+| SKL-EXEC-11 | Complexity-based behavior | Need low/medium/high behavior details |
+| SKL-EXEC-12 | Error handling | Build/test failure or cancellation |
 | COR-CS-1 | Complexity scoring table | Interpreting phase complexity |
 | TLS-PLN-1 | Plan mode switching | Before each phase |
 | TLS-PLN-2 | Plan mode workflow | Presenting phase details |
+| COR-CG-1 | Compaction guide purpose | When compacting at phase boundaries |
+| COR-CG-2 | Preserve rules | Crafting compact summary — what to keep |
+| COR-CG-3 | Discard rules | Crafting compact summary — what to drop |
+| COR-CG-4 | Compact summary template | Structuring compact instructions |
+| COR-PI-1 | Phase isolation architecture | Understanding isolated sub-agent flow |
+| COR-PI-2 | Sub-agent context template | Preparing focused prompt for sub-agent |
+| COR-PI-3 | Return format schema | Parsing sub-agent JSON response |
+| COR-PI-4 | Coordinator processing rules | Handling success/failure/partial returns |
 
 ### Expansion Instructions
 
@@ -465,3 +479,13 @@ Routing happens at Step 4 of the execution skill — the phase implementation is
 
 Disable with `/flow model_routing=false`. See `.claude/resources/core/model-routing.md` for full tier table, platform mappings, and aggregation rules.
 
+---
+
+## Phase Isolation
+
+When `phase_isolation: true` in `flow/.flowconfig` (default), each phase implementation runs in an **isolated Agent sub-agent** with a clean context window. The sub-agent receives only: phase spec, files modified so far, pattern file paths, and design context (if UI phase). It returns a structured JSON summary (1-2K tokens) with status, files changed, decisions, errors, and captured patterns.
+
+This eliminates context rot — phase 7 has the same quality as phase 1. Planning/approval stays in the main session; only the implementation step is isolated.
+
+Disable with `/flow phase_isolation=false`. See `.claude/resources/core/phase-isolation.md` for the full context template, return format schema, and coordinator processing rules.
+

package/.claude/commands/flow.md

@@ -40,6 +40,7 @@ SETTINGS:
   push=true|false        Auto-push after all phases + build/test pass (default: false)
   branch=<name>          Target branch for git operations (default: current branch)
   model_routing=true|false  Auto-select model per phase based on complexity (default: true)
+  phase_isolation=true|false  Run each phase in isolated sub-agent with clean context (default: true)
 
 COST REPORTING:
   /flow cost                             Last 7 days summary (default)
@@ -57,6 +58,7 @@ EXAMPLES:
   /flow branch=development                # Set target branch
   /flow commit=false push=false           # Disable git control
   /flow model_routing=false               # Disable model routing (use session model for all phases)
+  /flow phase_isolation=false             # Disable phase isolation (inline execution, for debugging)
   /flow cost                              # Show cost report (last 7 days)
   /flow cost --today --detail             # Today's costs with model breakdown
   /flow -status                           # Show current config
@@ -110,6 +112,7 @@ Parse the user input to determine what action to take:
 | `push` | `true`, `false` | `false` | Auto-push after completion |
 | `branch` | any string | current branch | Target branch for git ops |
 | `model_routing` | `true`, `false` | `true` | Auto-select model per phase based on complexity |
+| `phase_isolation` | `true`, `false` | `true` | Run each phase in isolated sub-agent with clean context |
 
 ---
 
@@ -239,6 +242,8 @@ autopilot: false
 commit: false
 push: false
 branch: ""
+model_routing: true
+phase_isolation: true
 ```
 
 **Location**: `flow/.flowconfig`

package/.claude/commands/heartbeat.md

@@ -53,7 +53,7 @@ TASKLIST INTEGRATION:
 
 RELATED COMMANDS:
   /flow           Configure plan-flow settings
-  /brain          Manual brain entry
+  /note           Manual brain entry
 ```
 
 ---

package/.claude/commands/learn.md

@@ -26,11 +26,10 @@ This command has two modes:
 | User Input | Mode | What To Do |
 |------------|------|------------|
 | `/learn` (no arguments) | **Pattern Extraction** | Scan session for reusable patterns (Steps 1-4 below) |
-| `/learn about <topic>` | **Teaching Mode** | Create a step-by-step curriculum to TEACH the user about `<topic>` |
-| `/learn <topic>` (any text after /learn) | **Teaching Mode** | Same as above — treat any argument as a topic to teach |
+| `/learn <topic>` (any text after /learn) | **Teaching Mode** | Create a step-by-step curriculum to TEACH the user about `<topic>` |
 | `/learn -help` | Help | Show help and stop |
 
-**Rule**: If the user provides ANY topic after `/learn`, you are in **Teaching Mode**. The ONLY way to trigger Pattern Extraction is `/learn` with no arguments.
+**Rule**: If the user provides ANY text after `/learn`, you are in **Teaching Mode**. The ONLY way to trigger Pattern Extraction is `/learn` with no arguments.
 
 **Teaching Mode means**: You are a TEACHER. You create a structured curriculum and teach the user step by step. You do NOT extract patterns from the session. You do NOT create `learned-*.md` files. You CREATE a curriculum and TEACH.
 
@@ -49,8 +48,7 @@ DESCRIPTION:
 
 USAGE:
   /learn                  Analyze session and suggest patterns to extract
-  /learn about <topic>    Teach me about <topic> step by step
-  /learn <topic>          Same as above — teach me about <topic>
+  /learn <topic>          Teach me about <topic> step by step
   /learn -help            Show this help
 
 PATTERN EXTRACTION MODE (/learn):
@@ -81,7 +79,7 @@ TEACHING MODE (/learn about <topic>):
   Index:  ~/plan-flow/brain/learns/_index.md (LRN-* codes)
 
 RELATED COMMANDS:
-  /brain           Capture meeting notes, ideas, brainstorms
+  /note            Capture meeting notes, ideas, brainstorms
   /setup           Generate project pattern files
   /review-code     Review local uncommitted changes
 ```

package/.claude/commands/{brain.md → note.md}

@@ -1,8 +1,8 @@
 ---
-description: Manual brain entry - capture meeting notes, ideas, brainstorms, and insights into the project brain
+description: Manual note entry - capture meeting notes, ideas, brainstorms, and insights into the project brain
 ---
 
-# Brain: Manual Knowledge Capture
+# Note: Manual Knowledge Capture
 
 ## Command Description
 
@@ -18,25 +18,25 @@ This command allows manual brain entries for capturing meeting notes, brainstorm
 **If the user invokes this command with `-help`, display only this section and stop:**
 
 ```
-/brain - Manual Brain Entry
+/note - Manual Brain Entry
 
 DESCRIPTION:
   Capture meeting notes, brainstorms, ideas, and insights into the
   project brain. Creates Obsidian-compatible markdown with [[wiki-links]].
 
 USAGE:
-  /brain <free text>        Free-text mode (default)
-  /brain -guided            Guided mode with structured questions
-  /brain -help              Show this help
+  /note <free text>        Free-text mode (default)
+  /note -guided            Guided mode with structured questions
+  /note -help              Show this help
 
 ARGUMENTS:
   free text     Unstructured text to parse and categorize
   -guided       Triggers structured question mode
 
 EXAMPLES:
-  /brain Had a call with the team about auth flow. Decision: use JWT with refresh tokens.
-  /brain Discovered that the API rate limits at 100 req/min. Need to add throttling.
-  /brain -guided
+  /note Had a call with the team about auth flow. Decision: use JWT with refresh tokens.
+  /note Discovered that the API rate limits at 100 req/min. Need to add throttling.
+  /note -guided
 
 OUTPUT:
   - Writes to appropriate flow/brain/ subdirectory
@@ -90,7 +90,7 @@ If no content and no `-guided` flag, ask:
 ```markdown
 What would you like to capture? You can:
 1. Type free text and I'll categorize it automatically
-2. Use `/brain -guided` for structured prompts
+2. Use `/note -guided` for structured prompts
 ```
 
 ---
@@ -175,7 +175,7 @@ Brain entry captured!
 
 ```
 +------------------------------------------+
-|           /brain COMMAND                 |
+|           /note COMMAND                  |
 +------------------------------------------+
                     |
                     v
@@ -214,7 +214,7 @@ Brain entry captured!
 
 ### Recommended Loading Order
 
-1. **Always load first**: This command file (`commands/brain.md`)
+1. **Always load first**: This command file (`commands/note.md`)
 2. **Load indexes**: Load `_index.md` files for relevant folders
 3. **Expand on-demand**: Use reference codes to load specific sections when needed
 

package/.claude/commands/review-code.md

@@ -46,6 +46,11 @@ WORKFLOW:
   4. Compares against existing patterns
   5. Generates review document with findings
 
+ADAPTIVE DEPTH:
+  < 50 lines    Lightweight (security, logic bugs, breaking changes only)
+  50-500 lines  Standard (full review)
+  500+ lines    Deep (multi-pass, severity-grouped, executive summary)
+
 REVIEW CATEGORIES:
   - Pattern compliance
   - Code quality issues
@@ -145,10 +150,24 @@ This command uses hierarchical context loading to reduce context consumption. In
 
 | Code | Description | When to Expand |
 |------|-------------|----------------|
-| SKL-REV-1 | Review code skill workflow | Understanding full process |
+| SKL-REV-1 | Purpose and restrictions | Understanding allowed actions |
+| SKL-REV-2 | Identify changed files | Starting the review |
+| SKL-REV-3 | Determine review depth | Adaptive depth selection |
+| SKL-REV-5 | Find similar implementations | Searching for comparable code |
+| SKL-REV-7 | Pattern conflicts + verify + re-rank | Processing findings |
+| SKL-REV-8 | Generate review document | Creating the output file |
+| SKL-REV-9 | Severity and conflict resolution | Severity levels and resolution options |
 | PTN-REV-1 | Review document structure | Creating review output |
 | COR-AP-1 | Allowed patterns overview | Checking pattern compliance |
 | COR-FP-1 | Forbidden patterns overview | Identifying anti-patterns |
+| COR-MA-1 | Multi-agent subagent definitions | Deep mode parallel review setup |
+| COR-MA-2 | Coordinator dedup and merge | Deep mode result processing |
+| COR-SR-1 | Severity re-ranking algorithm | Ordering findings by impact |
+| COR-SR-2 | Finding grouping rules | Grouping related findings |
+| COR-AD-1 | Adaptive depth size detection | Determining review mode |
+| COR-AD-2 | Lightweight review mode | Changeset < 50 lines |
+| COR-AD-3 | Deep review mode | Changeset 500+ lines |
+| COR-CG-1 | Compaction guide | Load when compacting mid-review |
 
 ### Expansion Instructions
 
@@ -241,6 +260,47 @@ Only save if the user approves. Do not re-ask if declined.
 
 ---
 
+## Multi-Agent Parallel Review
+
+For Deep mode reviews (500+ lines), the review is split into 4 specialized subagents running in parallel:
+
+| Agent | Focus | Model |
+|-------|-------|-------|
+| Security | Vulnerabilities, secrets, injection, auth bypass | sonnet |
+| Logic & Bugs | Edge cases, null handling, race conditions, wrong logic | sonnet |
+| Performance | N+1 queries, memory leaks, blocking I/O, re-renders | sonnet |
+| Pattern Compliance | Forbidden/allowed patterns, naming, consistency | haiku |
+
+The coordinator merges results, deduplicates overlapping findings, then runs verification and re-ranking.
+
+See `.claude/resources/core/review-multi-agent.md` for full rules.
+
+---
+
+## Adaptive Depth
+
+Review depth scales automatically based on changeset size:
+
+| Lines Changed | Mode | Behavior |
+|--------------|------|----------|
+| < 50 | **Lightweight** | Quick-scan for security, logic bugs, breaking changes only. Skips pattern loading, similar implementations, verification pass. |
+| 50–500 | **Standard** | Full review (current behavior, no changes). |
+| 500+ | **Deep** | Multi-pass review with file categorization, severity-grouped output, executive summary, and mandatory verification pass. |
+
+Thresholds are hardcoded. The detected mode is displayed before the review starts.
+
+See `.claude/resources/core/review-adaptive-depth.md` for full rules and `.claude/resources/patterns/review-code-templates.md` for lightweight and deep templates.
+
+---
+
+## Verification Pass
+
+After initial analysis, all findings undergo a second-pass verification. Each finding is re-examined against 15 lines of surrounding context and classified as Confirmed, Likely, or Dismissed. False positives are filtered before output. A Verification Summary shows filter stats.
+
+See `.claude/resources/core/review-verification.md` for classification criteria, category-specific questions, and output format.
+
+---
+
 ## Pattern Capture
 
 During code review, silently watch for anti-patterns found in changed code, good patterns that should be documented, and pattern conflicts between new and existing code. Append captured patterns to `flow/resources/pending-patterns.md` without interrupting work.

package/.claude/commands/review-pr.md

@@ -49,6 +49,11 @@ WORKFLOW:
   5. Analyzes code changes
   6. Generates review document
 
+ADAPTIVE DEPTH:
+  < 50 lines    Lightweight (security, logic bugs, breaking changes only)
+  50-500 lines  Standard (full review)
+  500+ lines    Deep (multi-pass, severity-grouped, executive summary)
+
 REVIEW INCLUDES:
   - Summary of changes
   - Pattern compliance check
@@ -140,12 +145,26 @@ This command uses hierarchical context loading to reduce context consumption. In
 
 | Code | Description | When to Expand |
 |------|-------------|----------------|
-| SKL-PR-1 | Review PR skill workflow | Understanding full process |
+| SKL-PR-1 | Purpose and restrictions | Understanding allowed actions |
+| SKL-PR-2 | Authenticate for PR access | Setting up authentication |
+| SKL-PR-3 | Fetch PR info + determine depth | Getting PR data and review mode |
+| SKL-PR-5 | Analyze + verify + re-rank | Processing findings |
+| SKL-PR-6 | Generate review document | Creating the output file |
+| SKL-PR-7 | Output template | Review document structure |
+| SKL-PR-8 | Fix complexity scoring | Severity and complexity details |
+| SKL-PR-9 | Link format (GitHub/Azure DevOps) | Platform-specific link formats |
 | TLS-AUTH-1 | Auth tool configuration | Setting up authentication |
 | TLS-AUTH-2 | Authentication workflow | Authenticating to platform |
 | PTN-PR-1 | PR review patterns | Creating review output |
 | COR-AP-1 | Allowed patterns overview | Checking pattern compliance |
 | COR-FP-1 | Forbidden patterns overview | Identifying anti-patterns |
+| COR-MA-1 | Multi-agent subagent definitions | Deep mode parallel review setup |
+| COR-MA-2 | Coordinator dedup and merge | Deep mode result processing |
+| COR-SR-1 | Severity re-ranking algorithm | Ordering findings by impact |
+| COR-SR-2 | Finding grouping rules | Grouping related findings |
+| COR-AD-1 | Adaptive depth size detection | Determining review mode |
+| COR-AD-2 | Lightweight review mode | Changeset < 50 lines |
+| COR-AD-3 | Deep review mode | Changeset 500+ lines |
 
 ### Expansion Instructions
 
@@ -238,3 +257,44 @@ During this skill's execution, watch for valuable reference materials worth pres
 At natural break points, if you encounter information that could be useful for future development (API specs, architecture notes, config references, domain knowledge, etc.), ask the user: "I found something that could be useful for future reference: _{brief description}_. Should I save it to `flow/resources/`?"
 
 Only save if the user approves. Do not re-ask if declined.
+
+---
+
+## Multi-Agent Parallel Review
+
+For Deep mode reviews (500+ lines), the review is split into 4 specialized subagents running in parallel:
+
+| Agent | Focus | Model |
+|-------|-------|-------|
+| Security | Vulnerabilities, secrets, injection, auth bypass | sonnet |
+| Logic & Bugs | Edge cases, null handling, race conditions, wrong logic | sonnet |
+| Performance | N+1 queries, memory leaks, blocking I/O, re-renders | sonnet |
+| Pattern Compliance | Forbidden/allowed patterns, naming, consistency | haiku |
+
+The coordinator merges results, deduplicates overlapping findings, then runs verification and re-ranking.
+
+See `.claude/resources/core/review-multi-agent.md` for full rules.
+
+---
+
+## Adaptive Depth
+
+Review depth scales automatically based on changeset size:
+
+| Lines Changed | Mode | Behavior |
+|--------------|------|----------|
+| < 50 | **Lightweight** | Quick-scan for security, logic bugs, breaking changes only. Skips pattern loading, full analysis, verification pass. |
+| 50–500 | **Standard** | Full review (current behavior, no changes). |
+| 500+ | **Deep** | Multi-pass review with file categorization, severity-grouped output, executive summary, and mandatory verification pass. |
+
+Thresholds are hardcoded. The detected mode is displayed before the review starts.
+
+See `.claude/resources/core/review-adaptive-depth.md` for full rules.
+
+---
+
+## Verification Pass
+
+After initial analysis, all findings undergo a second-pass verification. Each finding is re-examined against 15 lines of surrounding context and classified as Confirmed, Likely, or Dismissed. False positives are filtered before output. A Verification Summary shows filter stats.
+
+See `.claude/resources/core/review-verification.md` for classification criteria, category-specific questions, and output format.

package/.claude/commands/setup.md

@@ -673,7 +673,17 @@ This command uses hierarchical context loading to reduce context consumption. In
 
 | Code | Description | When to Expand |
 |------|-------------|----------------|
-| SKL-SETUP-1 | Setup skill workflow | Understanding full process |
+| SKL-SETUP-1 | Purpose and critical approach | Understanding setup goals |
+| SKL-SETUP-2 | Scan project structure | Scanning files and directories |
+| SKL-SETUP-3 | Deep dependency analysis | Analyzing package dependencies |
+| SKL-SETUP-4 | Deep code analysis | Sampling files and extracting patterns |
+| SKL-SETUP-7 | Ask confirming questions | Presenting questions via Plan mode |
+| SKL-SETUP-8 | Generate pattern files | Creating framework/library pattern files |
+| SKL-SETUP-9 | Update core pattern files | Updating allowed/forbidden patterns |
+| SKL-SETUP-11 | Create analysis document | Generating project analysis doc |
+| SKL-SETUP-12 | Index documentation | Indexing project docs with reference codes |
+| SKL-SETUP-13 | Create flow folder | Setting up flow/ directory structure |
+| SKL-SETUP-14 | Present summary | Final setup summary output |
 | TLS-IQ-1 | Interactive questions overview | Before asking questions |
 | TLS-IQ-2 | Switch to Plan mode | Starting question session |
 | TLS-IQ-3 | Ask questions format | Asking confirmation questions |

package/.claude/resources/core/_index.md

@@ -5,8 +5,8 @@
 
 Core rules define the foundational coding standards that apply across the entire project. These include best practices to follow (allowed patterns), anti-patterns to avoid (forbidden patterns), and complexity scoring for implementation planning.
 
-**Total Files**: 14 files, ~2310 lines
-**Reference Codes**: COR-AP-1 through COR-DA-3
+**Total Files**: 22 files, ~3580 lines
+**Reference Codes**: COR-AP-1 through COR-DSA-3
 
 ---
 
@@ -118,6 +118,74 @@ Core rules define the foundational coding standards that apply across the entire
 | COR-DA-2 | Token extraction and UI detection rules | design-awareness.md | 182-260 |
 | COR-DA-3 | Discovery question flow and execution injection | design-awareness.md | 262-350 |
 
+### Review Verification (`review-verification.md`)
+
+| Code | Description | Source | Lines |
+|------|-------------|--------|-------|
+| COR-RV-1 | Verification logic, questions, and classification criteria | review-verification.md | 1-120 |
+| COR-RV-2 | Output format and insertion points | review-verification.md | 122-200 |
+
+### Review Multi-Agent (`review-multi-agent.md`)
+
+| Code | Description | Source | Lines |
+|------|-------------|--------|-------|
+| COR-MA-1 | Subagent definitions (security, logic, performance, patterns) with prompts and models | review-multi-agent.md | 30-130 |
+| COR-MA-2 | Coordinator behavior (spawn, collect, deduplicate, verify, rank, output) | review-multi-agent.md | 132-195 |
+| COR-MA-3 | Subagent input rules and diff splitting for very large changesets | review-multi-agent.md | 100-130 |
+| COR-MA-4 | Insertion points for review-code and review-pr skills | review-multi-agent.md | 197-220 |
+
+### Review Severity Re-Ranking (`review-severity-ranking.md`)
+
+| Code | Description | Source | Lines |
+|------|-------------|--------|-------|
+| COR-SR-1 | Ranking algorithm (severity → confidence → complexity) | review-severity-ranking.md | 14-26 |
+| COR-SR-2 | Grouping related findings (patterns, rules, format) | review-severity-ranking.md | 28-88 |
+| COR-SR-3 | Executive summary trigger and risk level derivation | review-severity-ranking.md | 90-120 |
+| COR-SR-4 | Output structure and insertion points | review-severity-ranking.md | 122-150 |
+
+### Compaction Guide (`compaction-guide.md`)
+
+| Code | Description | Source | Lines |
+|------|-------------|--------|-------|
+| COR-CG-1 | Purpose, core principle, and when to compact | compaction-guide.md | 3-20 |
+| COR-CG-2 | Preserve rules — what to keep during compaction | compaction-guide.md | 22-38 |
+| COR-CG-3 | Discard rules — what to drop during compaction | compaction-guide.md | 40-55 |
+| COR-CG-4 | Compact summary template and skill-specific examples | compaction-guide.md | 57-110 |
+
+### Session Scratchpad (`session-scratchpad.md`)
+
+| Code | Description | Source | Lines |
+|------|-------------|--------|-------|
+| COR-SS-1 | Purpose, session start behavior, and write triggers | session-scratchpad.md | 3-45 |
+| COR-SS-2 | File format and 50-line limit | session-scratchpad.md | 47-68 |
+| COR-SS-3 | Promotion rules, targets, and compaction integration | session-scratchpad.md | 70-95 |
+
+### Phase Isolation (`phase-isolation.md`)
+
+| Code | Description | Source | Lines |
+|------|-------------|--------|-------|
+| COR-PI-1 | Purpose, architecture overview, and coordinator flow | phase-isolation.md | 3-40 |
+| COR-PI-2 | Context template — what to include in sub-agent prompt | phase-isolation.md | 42-85 |
+| COR-PI-3 | Return format schema (JSON), field descriptions, failure example | phase-isolation.md | 87-140 |
+| COR-PI-4 | Coordinator processing (success/failure/partial), config, and rules | phase-isolation.md | 142-180 |
+
+### Discovery Sub-Agents (`discovery-sub-agents.md`)
+
+| Code | Description | Source | Lines |
+|------|-------------|--------|-------|
+| COR-DSA-1 | Agent definitions with prompt templates (Similar Features, API/Data, Schema/Types) | discovery-sub-agents.md | 30-130 |
+| COR-DSA-2 | Return format schema and Codebase Analysis section template | discovery-sub-agents.md | 132-190 |
+| COR-DSA-3 | Coordinator behavior (spawn, collect, merge, error handling) | discovery-sub-agents.md | 192-240 |
+
+### Review Adaptive Depth (`review-adaptive-depth.md`)
+
+| Code | Description | Source | Lines |
+|------|-------------|--------|-------|
+| COR-AD-1 | Size detection, line counting rules, and tier definitions | review-adaptive-depth.md | 14-47 |
+| COR-AD-2 | Lightweight review mode (< 50 lines) — checks, skips, output | review-adaptive-depth.md | 51-101 |
+| COR-AD-3 | Deep review mode (500+ lines) — categorization, passes, executive summary | review-adaptive-depth.md | 103-187 |
+| COR-AD-4 | Insertion points for review-code and review-pr skills | review-adaptive-depth.md | 189-205 |
+
 ---
 
 ## When to Expand
@@ -160,6 +228,34 @@ Core rules define the foundational coding standards that apply across the entire
 | COR-DA-1 | Need design context template or personality options |
 | COR-DA-2 | Need token extraction or UI detection heuristics |
 | COR-DA-3 | Need design question flow or execution injection rules |
+| COR-RV-1 | Need verification questions or classification criteria |
+| COR-RV-2 | Need verification output format or skill insertion points |
+| COR-MA-1 | Need subagent definitions or prompt templates for deep review |
+| COR-MA-2 | Need coordinator dedup/merge behavior |
+| COR-MA-3 | Need subagent input rules or diff splitting strategy |
+| COR-MA-4 | Need multi-agent insertion points for review skills |
+| COR-SR-1 | Need ranking algorithm for review findings |
+| COR-SR-2 | Need grouping rules for related findings |
+| COR-SR-3 | Need executive summary trigger conditions |
+| COR-SR-4 | Need severity re-ranking output structure or insertion points |
+| COR-CG-1 | Need to understand when and why to compact |
+| COR-CG-2 | Need preserve rules for crafting compact summaries |
+| COR-CG-3 | Need discard rules for dropping low-signal tokens |
+| COR-CG-4 | Need compact summary template or skill-specific examples |
+| COR-AD-1 | Need size detection thresholds or line counting rules |
+| COR-AD-2 | Need lightweight review mode behavior |
+| COR-AD-3 | Need deep review mode behavior (categorization, passes, executive summary) |
+| COR-AD-4 | Need insertion points for adaptive depth in review skills |
+| COR-SS-1 | Need scratchpad purpose, session start behavior, or write triggers |
+| COR-SS-2 | Need scratchpad file format or size limit |
+| COR-SS-3 | Need scratchpad promotion rules or compaction integration |
+| COR-PI-1 | Need phase isolation architecture or coordinator flow |
+| COR-PI-2 | Need sub-agent context template (what to include in prompt) |
+| COR-PI-3 | Need return format schema or field descriptions |
+| COR-PI-4 | Need coordinator processing rules or config settings |
+| COR-DSA-1 | Need discovery sub-agent definitions or prompt templates |
+| COR-DSA-2 | Need return format schema or Codebase Analysis section template |
+| COR-DSA-3 | Need coordinator spawn/collect/merge behavior or error handling |
 
 ---
 
@@ -200,5 +296,9 @@ Core rules define the foundational coding standards that apply across the entire
 - `pattern-capture.md` is loaded on-demand - silently captures patterns during skill execution and presents for approval
 - `model-routing.md` is loaded on-demand - automatic model selection per phase based on complexity scores during `/execute-plan`
 - `project-tasklist.md` is loaded on-demand - session start tasklist behavior
+- `compaction-guide.md` is loaded on-demand - preserve/discard rules and summary template for `/compact`
+- `session-scratchpad.md` is loaded on-demand - ephemeral per-session notes with promotion to permanent storage
+- `phase-isolation.md` is loaded on-demand - isolated sub-agent execution per phase during `/execute-plan`
 - `project-memory.md` is loaded on-demand - artifact tracking and 7-day session loading
 - `heartbeat.md` is loaded on-demand - scheduled task daemon configuration
+- `discovery-sub-agents.md` is loaded on-demand - parallel codebase exploration sub-agents during `/discovery-plan`