@tgoodington/intuition 9.2.0 → 9.2.2

package/docs/project_notes/trunk/scratch/devops-infrastructure-research-plan.md

@@ -0,0 +1,7 @@
+## Research Plan
+
+### R1: Script structure and skill deployment mechanism
+Examine the install and uninstall scripts (`scripts/install-skills.js` and `scripts/uninstall-skills.js`) to understand the exact data-driven skill list arrays, legacy cleanup logic, and how skill folders are deployed to `~/.claude/skills/`. Also check `package.json` for any phase-name references in description, scripts, or other fields. This is needed to produce exact line-change specifications for T6 and to know what legacy cleanup entries already exist as a pattern to follow.
+
+### R2: Codebase-wide "plan" reference patterns in skills, scripts, and config
+Survey all files outside of `specialists/` and `producers/` (since those are confirmed clean) for occurrences of "plan" that could be phase-name references. Focus on: skill SKILL.md files, handoff routing, state schema/migration handlers, docs, and any other config. This provides the raw data for T1's categorized hit list and establishes the baseline for T8's verification sweep. Look specifically for the patterns identified in Known Research: `/intuition-plan`, `planning phase`, `"planning"` as JSON key, `plan.md`, `planning_brief.md`, `.planning_research/`, `status == "planning"`.

package/docs/project_notes/trunk/scratch/devops-infrastructure-stage1.md

@@ -0,0 +1,164 @@
+# DevOps Infrastructure — Stage 1 Exploration
+
+## Research Findings
+
+### Script Architecture
+- **install-skills.js**: Data-driven skill list array (lines 44-60). `intuition-plan` at line 48. Legacy cleanup block (lines 98-110) already handles `intuition-discovery` and `intuition-execute` removal using `fs.existsSync` + `fs.rmSync` pattern. Help text at line 188 describes the plan skill.
+- **uninstall-skills.js**: Parallel skill removal array (lines 44-64). `intuition-plan` at line 48. Already has legacy entries for `intuition-execute` (v8.0) and `intuition-discovery` (v6.0). Needs `intuition-plan` added to legacy section after renaming active entry.
+- **package.json**: Description at line 4 contains "plan" in "prompt, plan, assemble specialist teams" — this is a phase-name reference requiring rename. Keywords at line 8 contain "planning" — this is generic English describing the package's purpose (planning is what the tool does, regardless of internal phase naming).
+
+### Codebase Blast Radius
+- **177 lines across 39 files** contain "plan" references.
+- **~165 instances** are phase-name references requiring rename.
+- **~12 instances** are generic English that must be preserved.
+- **Specialists and producers**: Confirmed zero phase-name references (clean).
+- **Heaviest files**: `intuition-plan/SKILL.md` (78 lines), `intuition-handoff/SKILL.md` (48 lines), `handoff_core.md` reference file (12+ lines).
+
+### File and Directory Rename Targets
+- Folder: `skills/intuition-plan/` → `skills/intuition-outline/`
+- Output files: `plan.md` → `outline.md`, `planning_brief.md` → `outline_brief.md`
+- Research directory: `.planning_research/` → `.outline_research/`
+- State field: `"planning"` key → `"outline"` key
+- State status value: `"planning"` → `"outline"`
+
+### Disambiguation Patterns Confirmed
+Phase-name patterns (rename): `/intuition-plan`, `planning phase` (when referring to the workflow phase), `"planning"` (JSON key/status), `plan.md` (file reference), `planning_brief.md`, `.planning_research/`, `status == "planning"`.
+
+Generic English patterns (preserve): "research plan," "ARCH planning," "planning context" (research context meaning), "action plan," "continue planning" (activity verb), "planning" in keywords.
+
+### Borderline Cases
+- `package.json` keywords "planning" — generic English (the package helps with planning activities, not a reference to the internal phase name).
+- `intuition-debugger/SKILL.md` "plan diverged from intent" — refers to the `plan.md` file artifact, so this IS a phase-name reference that should become "outline diverged from intent."
+
+## ECD Analysis
+
+### Elements
+1. **Install script** (`install-skills.js`) — deploys skills from package to `~/.claude/skills/`, has skill list array and legacy cleanup block.
+2. **Uninstall script** (`uninstall-skills.js`) — removes skills from `~/.claude/skills/`, has skill list array and legacy skill entries.
+3. **Package manifest** (`package.json`) — npm package metadata with description and keywords.
+4. **Skill list array** — single source of truth for which skills get deployed (data-driven pattern).
+5. **Legacy cleanup block** — removes old skill folders that were renamed/deleted in prior versions.
+6. **Help text** — user-facing skill descriptions printed during install.
+
+### Connections
+- Install script reads skill folders from `skills/` and deploys to `~/.claude/skills/` — the skill list array must match actual folder names.
+- Uninstall script's active list must mirror install script's list exactly.
+- Legacy cleanup in install script must handle the transition for users who have the old `intuition-plan` folder deployed.
+- Package description is user-facing (npm registry) — must reflect current phase naming.
+- Help text in install script is user-facing — must match deployed skill names.
+
+### Dynamics
+- **Upgrade path**: Users with existing `intuition-plan` in `~/.claude/skills/` will run `npm update`. The install script's postinstall hook fires. Legacy cleanup must remove old `intuition-plan` before deploying new `intuition-outline`. Without this, stale `intuition-plan` folder persists alongside `intuition-outline`.
+- **Fresh install**: No legacy cleanup needed; only `intuition-outline` is deployed.
+- **Uninstall path**: Must remove `intuition-outline` (active) AND `intuition-plan` (legacy, in case uninstall runs on a partially-migrated system).
+- **Ordering**: Legacy cleanup runs BEFORE skill deployment in the install script, which is correct — old folder removed, new folder deployed.
+
+## Assumptions
+
+### A1: Legacy cleanup ordering is correct
+- **Default**: The existing legacy cleanup block in `install-skills.js` runs before skill deployment, so adding `intuition-plan` to it will remove the old folder before the new `intuition-outline` folder is deployed.
+- **Rationale**: Research shows legacy cleanup at lines 98-110 and deployment loop follows after. The existing `intuition-discovery` and `intuition-execute` cleanup entries follow this same pattern successfully.
+
+### A2: Package.json keywords "planning" is generic English
+- **Default**: The keyword "planning" in package.json describes the package's purpose (it is a planning tool) and is not a reference to the internal phase name. It will be preserved.
+- **Rationale**: npm keywords describe package functionality for search/discovery. Users search for "planning" when looking for planning tools. Changing this to "outlining" would reduce discoverability and misrepresent the package's purpose. The internal rename from "plan phase" to "outline phase" does not change what the tool does.
+
+### A3: Debugger "plan diverged from intent" is a phase-name reference
+- **Default**: This reference in the debugger skill refers to the `plan.md` output artifact, so it should become "outline diverged from intent."
+- **Rationale**: In context, the debugger is diagnosing whether the plan document (the artifact) matches user intent. Since the artifact is being renamed from `plan.md` to `outline.md`, references to it should follow.
+
+## Key Decisions
+
+### D1: Version annotation for legacy cleanup comment
+- **Tier**: [SILENT]
+- **Options**:
+  - (a) Annotate as "renamed in v9.1" (matches known research suggestion)
+  - (b) Annotate as "renamed in v9.2" or just "v10"
+  - (c) No version annotation
+- **Recommendation**: Use "v9.1" — this is the version where the rename is being implemented, consistent with the project's existing pattern (`intuition-execute` is annotated "v8.0", `intuition-discovery` is annotated "v6.0").
+- **Risk if wrong**: Minor inconsistency in comments. No functional impact.
+
+### D2: Uninstall script legacy entry placement
+- **Tier**: [SILENT]
+- **Options**:
+  - (a) Add `intuition-plan` to the existing legacy comments section at the bottom of the uninstall array
+  - (b) Add `intuition-plan` as a separate legacy block outside the array
+- **Recommendation**: Option (a) — add to the existing legacy section in the uninstall array, following the pattern of `intuition-execute` and `intuition-discovery`.
+- **Risk if wrong**: No functional risk; purely organizational.
+
+### D3: Package.json description wording
+- **Tier**: [SILENT]
+- **Options**:
+  - (a) Replace "plan" with "outline" → "prompt, outline, assemble specialist teams"
+  - (b) Reword entirely → "prompt, outline, assemble and coordinate specialist teams"
+  - (c) Keep "plan" as generic English
+- **Recommendation**: Option (a) — minimal change, direct substitution. "Prompt, outline, assemble specialist teams" reads naturally and matches the new phase name.
+- **Risk if wrong**: Cosmetic only. npm description is low-stakes.
+
+### D4: Help text update in install script
+- **Tier**: [SILENT]
+- **Options**:
+  - (a) Rename to `/intuition-outline` and update description to match
+  - (b) Just rename the skill name, keep description as-is
+- **Recommendation**: Option (a) — update both the skill name and description. The description "Strategic planning (ARCH protocol + design flagging)" should become "Strategic outlining (ARCH protocol + design flagging)" or similar to maintain consistency.
+- **Risk if wrong**: User confusion if help text doesn't match deployed skill name.
+
+## Risks Identified
+
+1. **Stale deployment on upgrade**: If legacy cleanup is not added to the install script, users who upgrade will have BOTH `intuition-plan` and `intuition-outline` in `~/.claude/skills/`. The old one would still be invocable via `/intuition-plan`, causing confusion. **Mitigation**: T6 explicitly adds legacy cleanup entry.
+
+2. **Grep false negatives in T1/T8**: Some phase-name references may use unusual patterns not covered by the standard grep queries (e.g., concatenated strings, template literals). **Mitigation**: Use multiple grep patterns and manually inspect borderline hits. T8 verification sweep is the safety net.
+
+3. **Generic English false positives**: Aggressive grep patterns could flag generic English "plan" uses for rename, breaking natural language in documentation and skill instructions. **Mitigation**: The disambiguation guide from Known Research is thorough. Each hit must be individually categorized before any changes are made.
+
+4. **Partial rename state**: If the rename is applied to some files but not others (interrupted work), cross-references break. **Mitigation**: T8 verification sweep checks for zero stale references AND valid cross-references. Tasks should be executed in order (T1 audit first, T6 scripts, then T8 verification).
+
+## Recommended Approach
+
+### T1: Audit all phase-name references
+
+**Grep Pattern Set** (run each across the full codebase, excluding `node_modules/`, `.git/`, `specialists/`, `producers/`):
+1. `intuition-plan` — skill name references (folders, routing, slash commands)
+2. `planning_brief` — file name references
+3. `plan\.md` — output file references (escaped dot to avoid "plan.markdown" etc.)
+4. `\.planning_research` — research directory references
+5. `"planning"` — JSON key/status value references
+6. `planning phase` — prose phase-name references
+7. `planning →` or `→ planning` — workflow diagram references
+
+**Categorization method**: For each hit, apply the disambiguation rules from Known Research. Mark as RENAME if it matches a phase-name pattern, KEEP if it matches a generic English pattern, BORDERLINE if unclear (with rationale).
+
+**Output format**: Markdown table grouped by file, with columns: File | Line | Content | Category (RENAME/KEEP) | Notes.
+
+### T6: Update scripts and package config
+
+**install-skills.js changes**:
+1. Line 48: `'intuition-plan'` → `'intuition-outline'` in skill list array
+2. Lines 98-110 area: Add new legacy cleanup block for `intuition-plan` (following exact pattern of `intuition-discovery`/`intuition-execute` blocks)
+3. Line 188: Update help text from `/intuition-plan` to `/intuition-outline` with updated description
+
+**uninstall-skills.js changes**:
+1. Line 48: `'intuition-plan'` → `'intuition-outline'` in active skill list
+2. Add `'intuition-plan'` to legacy skill entries section (after `intuition-discovery`)
+
+**package.json changes**:
+1. Line 4 description: "plan" → "outline" in the phase enumeration
+
+**Verification**: After changes, confirm `intuition-outline` appears in both script arrays and `intuition-plan` appears in both legacy sections.
+
+### T8: Verification sweep
+
+**Phase 1 — Zero stale references**: Re-run the exact same grep pattern set from T1. Every hit must be either (a) categorized as KEEP in T1, or (b) gone. Any RENAME hits remaining indicate incomplete work.
+
+**Phase 2 — Structural verification**:
+- Confirm `skills/intuition-outline/SKILL.md` exists with correct frontmatter
+- Confirm `skills/intuition-plan/` does NOT exist
+- Confirm install script skill list includes `intuition-outline`
+- Confirm uninstall script skill list includes `intuition-outline`
+- Confirm both scripts have `intuition-plan` in legacy sections
+
+**Phase 3 — Migration handler**: Validate that the v7→v8 state migration handler in handoff correctly transforms `"planning"` → `"outline"` in a sample state object. Test with a minimal JSON fixture.
+
+**Phase 4 — Cross-reference integrity**: For each skill that references outline artifacts (`outline.md`, `outline_brief.md`, `.outline_research/`), confirm the referenced file names are consistent across all skills that produce or consume them.
+
+**Output**: Verification report with PASS/FAIL for each check, plus any anomalies found.

package/docs/project_notes/trunk/scratch/technical-writer-decisions.json

@@ -0,0 +1,88 @@
+{
+  "specialist": "technical-writer",
+  "gate_started": "2026-03-04T19:30:00.000Z",
+  "gate_completed": "2026-03-04T19:35:00.000Z",
+  "decision_policy": "aggressive",
+  "assumptions": [
+    {
+      "id": "A1",
+      "title": "Detail skill 'research plan' terminology is generic English",
+      "default": "All instances of 'research plan', 'research-plan.md', 'Research Planning', 'research-planning framing' in intuition-detail/SKILL.md are KEPT unchanged",
+      "status": "accepted",
+      "user_override": null
+    },
+    {
+      "id": "A2",
+      "title": "Named section headings rename alongside the file",
+      "default": "PLAN.MD OUTPUT FORMAT → OUTLINE.MD OUTPUT FORMAT, Planning Context for Engineer → Outline Context for Engineer",
+      "status": "accepted",
+      "user_override": null
+    },
+    {
+      "id": "A3",
+      "title": "MEMORY.md gets same disambiguation treatment as other docs",
+      "default": "Phase-name references renamed, generic English preserved",
+      "status": "accepted",
+      "user_override": null
+    },
+    {
+      "id": "A4",
+      "title": "Deprecated skills receive full rename, deprecation notices unchanged",
+      "default": "All phase-name references in design/engineer skills renamed; [v8 compat] deprecation notice text not modified",
+      "status": "accepted",
+      "user_override": null
+    }
+  ],
+  "decisions": [
+    {
+      "id": "D1",
+      "title": "YAML frontmatter description rewording for intuition-outline",
+      "tier": "SPEC",
+      "classified_by": "plan",
+      "context": "Current description has no literal 'plan' word",
+      "options": ["Leave unchanged (minimal)", "Light reword to mention outline", "Full rewrite"],
+      "chosen": "Leave unchanged (minimal)",
+      "user_input": null
+    },
+    {
+      "id": "D2",
+      "title": "Treatment of compound terms 'build plan' and 'test plan'",
+      "tier": "SPEC",
+      "classified_by": "detail",
+      "context": "These are standard English for execution strategy, not phase references",
+      "options": ["Leave as-is", "Reword to 'build strategy' / 'test strategy'", "Reword to 'build sequence' / 'test approach'"],
+      "chosen": "Leave as-is",
+      "user_input": null
+    },
+    {
+      "id": "D3",
+      "title": "Treatment of classified_by: 'plan' metadata in detail skill",
+      "tier": "SILENT",
+      "classified_by": "detail",
+      "context": "Phase-name reference in metadata value",
+      "options": ["Rename to 'outline'", "Leave as 'plan'"],
+      "chosen": "Rename to 'outline'",
+      "user_input": null
+    },
+    {
+      "id": "D4",
+      "title": "Whether deprecated skills need deprecation notice updates",
+      "tier": "SPEC",
+      "classified_by": "plan",
+      "context": "Deprecation notices don't mention plan phase by name",
+      "options": ["No change to notices", "Add rename note to notices"],
+      "chosen": "No change to notices",
+      "user_input": null
+    },
+    {
+      "id": "D5",
+      "title": "Treatment of 'Layer 2: Plan' in design doc",
+      "tier": "SILENT",
+      "classified_by": "plan",
+      "context": "Conceptual layer name in domain-adaptive-team-architecture.md",
+      "options": ["Rename to 'Layer 2: Outline'", "Keep as 'Layer 2: Plan'"],
+      "chosen": "Rename to 'Layer 2: Outline'",
+      "user_input": null
+    }
+  ]
+}

package/docs/project_notes/trunk/scratch/technical-writer-research-plan.md

@@ -0,0 +1,7 @@
+## Research Plan
+
+### R1: Current content of the outline skill (intuition-plan/SKILL.md) and initialize skill template
+Read `skills/intuition-plan/SKILL.md` and `skills/intuition-initialize/SKILL.md` to map every line containing "plan", "planning", "plan.md", "planning_brief", ".planning_research" — needed to produce exact line-level change specifications for T2 and T4. Also need to see the YAML frontmatter structure and state template format.
+
+### R2: All remaining skills and documentation files containing plan-phase references
+Scan the 9 other skills (start, prompt, assemble, detail, build, test, design, engineer, debugger, handoff) plus docs/v9/*.md, MEMORY.md, and any root-level docs (ARCHITECTURE_OVERVIEW.txt) for lines matching "plan" to build per-file change lists for T5 and T7. Need to see surrounding context to apply the disambiguation rule correctly. Focus on: `skills/intuition-*/SKILL.md`, `docs/v9/*.md`, `MEMORY.md`, `ARCHITECTURE_OVERVIEW.txt`.

package/docs/project_notes/trunk/scratch/technical-writer-stage1.md

@@ -0,0 +1,266 @@
+# Technical Writer — Stage 1 Exploration
+
+## Research Findings
+
+### RF1: intuition-plan/SKILL.md (T2 — the core rename target)
+
+The file has ~78 lines requiring rename across these categories:
+
+1. **YAML frontmatter** (2 lines): `name: intuition-plan` and `description` field
+2. **Output file paths** (~20 lines): `plan.md`, `planning_brief.md`, `.planning_research/`, `.planning_research/orientation.md`, `.planning_research/decision_[domain].md`, `.planning_research/decisions_log.md`, `.planning_research/parent_intersection.md`
+3. **Phase-name references** (~25 lines): "planning phase", "planning is precise work", "planning depth tier", "planning architect", "plan-level decision"
+4. **Artifact references** (~25 lines): "final plan", "parent plan", "draft plan", "approved plan", "the plan does NOT reference..."
+5. **Section/heading names** (~6 lines): "PLAN.MD OUTPUT FORMAT", "Planning Context for Engineer"
+6. **Generic KEEP** (1 line): Line 14 — a generic file path reference unrelated to phase naming
+
+The heading "Planning Context for Engineer" (line 194 area and Section 10) is a named section within the plan.md output format. Since plan.md becomes outline.md, this heading should become "Outline Context for Engineer".
+
+### RF2: intuition-initialize/SKILL.md (T4)
+
+Minimal changes needed:
+- Line 137 area: `"planning"` key in state template JSON becomes `"outline"`
+- Version string: `"7.0"` becomes `"8.0"`
+- All sub-fields (started, completed, completed_at, approved) are preserved as-is
+
+### RF3: Remaining 9 skills (T5)
+
+Per-file RENAME counts and notable disambiguation:
+
+| Skill | RENAME | KEEP | Notable |
+|-------|--------|------|---------|
+| intuition-start | 9 | 0 | State field refs: `workflow.planning.*`, status enum "planning" |
+| intuition-prompt | 10 | 1 | "plan against" at line 114 is generic English (KEEP) |
+| intuition-assemble | 12 | 0 | `plan.md` artifact refs, `/intuition-plan` routing |
+| intuition-detail | 25 | 1 | Critical: `research-plan.md`, "Research Planning" sub-stage, "research-planning framing" are ALL generic English (KEEP). `classified_by: "plan"` IS phase-name (RENAME). |
+| intuition-build | 15 | 1 | "build plan" is borderline — see D2 below |
+| intuition-test | 12 | 0 | "test plan" is borderline — see D2 below |
+| intuition-design | 11 | 0 | Deprecated [v8 compat] skill |
+| intuition-engineer | 22 | 0 | Deprecated [v8 compat] skill; "Planning Context for Engineer" section name |
+| intuition-debugger | 14 | 0 | "plan diverged from intent" confirmed as RENAME by prior blueprint |
+| intuition-handoff | 48 | 0 | Heaviest file after plan itself; state schema, transitions, mode detection |
+
+**Total across 10 skills (excluding plan itself):** ~178 RENAME, ~3 KEEP
+
+### RF4: Documentation files (T7)
+
+| File | RENAME | KEEP | Notable |
+|------|--------|------|---------|
+| decision-framework-direction.md | 5 | 1 | "research planning" at line 96 is KEEP |
+| decision-framework-implementation.md | 7 | 0 | Clean phase-name refs |
+| domain-adaptive-team-architecture.md | 11 | 0 | "Layer 2: Plan" conceptual name becomes "Layer 2: Outline" |
+| ARCHITECTURE_OVERVIEW.txt | 19 | 1 | "Waldo doesn't plan" at line 282 is KEEP |
+| README.md | 10 | 0 | |
+| TESTING_README.md | 7 | 0 | |
+| TESTING_SUMMARY.md | 25 | 0 | Heavy density of plan refs |
+| MEMORY.md | ~30+ | ~5 | Heaviest doc file; many generic English uses too |
+
+### RF5: The detail skill disambiguation challenge
+
+The `intuition-detail/SKILL.md` file has the highest disambiguation complexity:
+- `research-plan.md` (file artifact name for the specialist's research plan) — KEEP. This is "a plan for research," not "the plan phase."
+- `Research Planning` (sub-stage 1a name) — KEEP. This is "planning what to research."
+- `research-planning framing` — KEEP.
+- `classified_by: "plan"` — RENAME to `classified_by: "outline"`. This means "classified by the plan/outline phase."
+- `plan's Decisions field`, `plan Section 10`, `planning phase` — RENAME. Direct phase references.
+
+### RF6: Compound terms "build plan" and "test plan"
+
+In `intuition-build/SKILL.md`, "build plan" appears at lines 20, 61, 106, 109 meaning "the builder's execution strategy." In `intuition-test/SKILL.md`, "test plan" appears at lines 44, 102, 161, 181, 184, 197, 203 meaning "the testing strategy." Neither refers to the planning phase or plan.md artifact.
+
+These are technically generic English ("a plan for building/testing"), but they create potential confusion with the now-renamed outline phase because readers may wonder whether "build plan" refers to an artifact called plan.md.
+
+## ECD Analysis
+
+### Elements (the discrete documentation artifacts being changed)
+
+1. **SKILL.md files** (12 total) — the primary behavioral instruction documents
+2. **State schema template** — JSON in initialize skill defining workflow field names
+3. **Design documents** (3 in docs/v9/) — architectural decision records
+4. **Root documentation** (4 files) — README, ARCHITECTURE_OVERVIEW, TESTING_README, TESTING_SUMMARY
+5. **MEMORY.md** — cross-conversation persistent memory
+6. **Named section headings** — e.g., "Planning Context for Engineer", "PLAN.MD OUTPUT FORMAT" which become "Outline Context for Engineer", "OUTLINE.MD OUTPUT FORMAT"
+
+### Connections (how these elements reference each other)
+
+- **Routing chains**: prompt mentions `/intuition-plan`, handoff routes to it, start detects `workflow.planning` state — all must rename in lockstep
+- **Artifact references**: many skills read `plan.md` — all must become `outline.md`
+- **State field coupling**: initialize template, handoff state writes, start state reads all share the `planning` / `outline` field name
+- **Section name coupling**: engineer reads "Planning Context for Engineer" from plan.md — both the producer (plan skill) and consumer (engineer skill) must rename this heading simultaneously
+- **Documentation echo**: MEMORY.md and docs/v9/ describe the same workflow that the skills implement — must stay synchronized
+
+### Dynamics (what can go wrong during the rename)
+
+1. **Partial rename breaks routing**: If handoff writes `status: "outline"` but start still checks `status == "planning"`, the workflow stalls silently
+2. **Disambiguation drift**: A builder applies the rename too aggressively and changes "research plan" to "research outline" in the detail skill, breaking the research sub-stage naming
+3. **Section name mismatch**: If plan skill outputs "Outline Context for Engineer" but engineer skill still reads "Planning Context for Engineer," the section won't be found
+4. **Compound term confusion**: "build plan" left as-is could confuse readers post-rename into thinking it references an artifact
+
+## Assumptions
+
+### A1: The detail skill's "research plan" terminology is firmly generic English
+- **Default**: All instances of "research plan," "research-plan.md," "Research Planning," and "research-planning framing" in intuition-detail/SKILL.md are KEPT unchanged.
+- **Rationale**: These describe the activity of planning research, not the outline phase. The research-plan.md artifact is produced by the specialist during Stage 1a and has no connection to the outline phase. Renaming these would damage the detail skill's three-sub-stage naming clarity.
+
+### A2: Named section headings in plan.md output format rename alongside the file
+- **Default**: "PLAN.MD OUTPUT FORMAT" becomes "OUTLINE.MD OUTPUT FORMAT". "Planning Context for Engineer" becomes "Outline Context for Engineer". "Planning Depth Tier" becomes "Outline Depth Tier".
+- **Rationale**: These are section names within or about the plan.md artifact. Since plan.md becomes outline.md, the section names should track. Consumers of these sections (engineer, design skills) must update their references simultaneously.
+
+### A3: MEMORY.md gets the same treatment as other documentation
+- **Default**: Phase-name references in MEMORY.md are renamed; generic English is preserved. MEMORY.md is treated as part of T7 documentation scope.
+- **Rationale**: MEMORY.md is auto-loaded into every conversation, so stale phase names there would be actively confusing. It contains both phase-name and generic English uses of "plan" and needs the same disambiguation discipline as other docs.
+
+### A4: Deprecated skills (design, engineer) receive full rename treatment
+- **Default**: All phase-name references inside deprecated skills are renamed, identical to active skills. The `[v8 compat]` deprecation notices are not modified beyond the phase-name rename.
+- **Rationale**: Even deprecated code should be internally consistent. If someone invokes these skills, they should reference the correct artifact names. The deprecation notice itself doesn't mention the plan phase by name so no change needed there.
+
+## Key Decisions
+
+### D1: YAML frontmatter description rewording for intuition-outline
+- **Tier**: [SPEC]
+- **Options**:
+  - (A) Minimal: change only `name: intuition-outline`, leave description text unchanged (it says "Strategic architect. Reads prompt brief..." with no literal "plan" word)
+  - (B) Light reword: update description to mention "outline" instead of "blueprint" to reinforce the rename
+  - (C) Full rewrite: rewrite description to center on "outline" terminology
+- **Recommendation**: Option A. The current description does not contain the word "plan" and accurately describes the skill's behavior. The name field change is sufficient. Unnecessary rewording risks introducing inaccuracy.
+- **Risk if wrong**: Minimal. The description is metadata, not behavioral instruction.
+
+### D2: Treatment of compound terms "build plan" and "test plan"
+- **Tier**: [SPEC]
+- **Options**:
+  - (A) Leave as-is: "build plan" and "test plan" are standard English compound nouns meaning execution strategies, not phase references
+  - (B) Reword to "build strategy" / "test strategy": eliminates any post-rename ambiguity with the outline phase
+  - (C) Reword to "build sequence" / "test approach": alternative wording
+- **Recommendation**: Option A (leave as-is). These are established English terms in software engineering. No reader would confuse "test plan" with the outline.md artifact. Rewording introduces unnecessary churn and may reduce clarity — "test plan" is universally understood, "test strategy" slightly less so. The disambiguation rule from the planning phase explicitly says generic English "plan" stays.
+- **Risk if wrong**: Minor reader confusion in the first few sessions post-rename. Easily corrected later if it proves problematic.
+
+### D3: Treatment of `classified_by: "plan"` metadata values in detail skill
+- **Tier**: [SILENT]
+- **Options**:
+  - (A) Rename to `classified_by: "outline"` — tracks the phase rename
+  - (B) Leave as `classified_by: "plan"` — it's a stored metadata value, not user-facing
+- **Recommendation**: Option A. This is a phase-name reference embedded in metadata. It means "this decision was classified by the outline phase." Consistency requires renaming it.
+- **Risk if wrong**: Mismatched metadata terminology, but no functional impact since it's a string label.
+
+### D4: Whether deprecated skills need deprecation notice updates
+- **Tier**: [SPEC]
+- **Options**:
+  - (A) No change to deprecation notices — they don't mention "plan" by name currently
+  - (B) Add a note like "formerly /intuition-plan, now /intuition-outline" to the deprecation block
+- **Recommendation**: Option A. The existing deprecation notices in design and engineer skills say `[v8 compat]` and mention the v9 replacement workflow without specifically naming `/intuition-plan`. Adding a rename note would be unnecessary clutter in already-deprecated code.
+- **Risk if wrong**: Someone reading the deprecated skill might not realize the plan phase was renamed. This is extremely low impact since the skills already direct users to the v9 workflow.
+
+### D5: Treatment of "Layer 2: Plan" in domain-adaptive-team-architecture.md
+- **Tier**: [SILENT]
+- **Options**:
+  - (A) Rename to "Layer 2: Outline"
+  - (B) Keep as "Layer 2: Plan" since it's a conceptual layer name in a design doc
+- **Recommendation**: Option A, per the known research disambiguation guidance which explicitly calls this out: "Layer 2: Plan is a conceptual layer name -- should become Layer 2: Outline."
+- **Risk if wrong**: None. The design doc is reference material, not executable.
+
+## Risks Identified
+
+### Risk 1: Detail skill research-plan disambiguation error
+- **Severity**: High
+- **Description**: The detail skill contains ~12 instances of "plan" in the research sub-stage context (research-plan.md, Research Planning, research-planning framing). An overzealous rename would break the three-sub-stage naming convention.
+- **Mitigation**: Builder must use the explicit disambiguation list from this blueprint. The KEEP items in detail are: any line containing "research plan", "research-plan.md", "Research Planning", "research-planning framing", and "specialist planned to use."
+
+### Risk 2: Section name mismatch between producer and consumer skills
+- **Severity**: Medium
+- **Description**: The plan skill produces a section called "Planning Context for Engineer." The engineer skill reads this section by name. If one is renamed without the other, the section lookup fails silently.
+- **Mitigation**: T2 (plan skill rename) and T5 (engineer skill rename) must both rename this heading. The T1 audit hit list should cross-reference producer/consumer pairs.
+
+### Risk 3: MEMORY.md high disambiguation density
+- **Severity**: Medium
+- **Description**: MEMORY.md has ~30+ rename candidates and ~5+ KEEP items in close proximity. It uses "plan" in both phase-name and generic English contexts heavily, sometimes in the same paragraph.
+- **Mitigation**: T7 builder should process MEMORY.md line-by-line with explicit classification for each instance. The known patterns from the disambiguation guidance apply: "ARCH planning" is KEEP, "plan.md" is RENAME, "v9 Phase Flow" line is RENAME, etc.
+
+### Risk 4: State field rename without migration path
+- **Severity**: Low (mitigated by T3)
+- **Description**: T4 changes the initialize template from `planning` to `outline`, but existing projects have state files with the `planning` field.
+- **Mitigation**: T3 (handoff migration, handled by devops-infrastructure blueprint) adds a v7->v8 migration handler. T4 only changes the template for new projects. These must be sequenced correctly (T3 before T4).
+
+## Recommended Approach
+
+### T2: Rename intuition-plan skill (folder + SKILL.md)
+
+**Execution order:**
+1. Rename the folder: `skills/intuition-plan/` to `skills/intuition-outline/`
+2. Update YAML frontmatter: `name: intuition-outline` (leave description unchanged per D1)
+3. Global replacements within the file (safe bulk operations):
+   - `plan.md` to `outline.md` (all instances)
+   - `planning_brief.md` to `outline_brief.md` (all instances)
+   - `.planning_research/` to `.outline_research/` (all instances)
+   - `.planning_research` (without trailing slash) to `.outline_research` (catch refs like `.planning_research` at end of sentence)
+   - `/intuition-plan` to `/intuition-outline` (all instances)
+4. Targeted replacements (context-sensitive, line-by-line):
+   - "PLAN.MD OUTPUT FORMAT" to "OUTLINE.MD OUTPUT FORMAT"
+   - "Planning Context for Engineer" to "Outline Context for Engineer"
+   - "planning depth tier" to "outline depth tier" (case-insensitive variants)
+   - "planning phase" to "outline phase"
+   - "planning architect" to "outline architect"
+   - "planning is precise work" to "outlining is precise work"
+   - "final plan" to "final outline"
+   - "parent plan" to "parent outline"
+   - "draft plan" to "draft outline"
+   - "approved plan" to "approved outline"
+   - "plan-level" to "outline-level"
+   - "the plan" (when referring to the artifact) to "the outline"
+   - "branch plans" to "branch outlines"
+   - "presenting the draft plan" to "presenting the draft outline"
+   - "from plan" to "from outline" (when artifact reference)
+5. Verify: Zero remaining "plan" phase-name references. The only "plan" remaining should be the 1 KEEP at line 14.
+
+### T4: Update initialize skill state template
+
+1. Change `"version": "7.0"` to `"version": "8.0"` in the state template JSON
+2. Change the `"planning"` key to `"outline"` in the workflow object
+3. Verify all sub-fields (started, completed, completed_at, approved) are unchanged
+
+This is a 2-line change. No disambiguation needed.
+
+### T5: Update all other skills (9 files)
+
+Process each file with the same bulk-then-targeted approach as T2. Per-file specifics:
+
+**intuition-start**: Rename `workflow.planning.*` to `workflow.outline.*`, `status == "planning"` to `status == "outline"`, `ready_for_planning` to `ready_for_outline`, `/intuition-plan` to `/intuition-outline`, `plan.md (planning done)` to `outline.md (outline done)`.
+
+**intuition-prompt**: Rename "planning-ready" to "outline-ready", `/intuition-plan` to `/intuition-outline`, "planning phase" to "outline phase", "Open questions for planning" to "Open questions for outlining". KEEP "plan against" at line 114.
+
+**intuition-assemble**: Rename all `plan.md` to `outline.md`, `plan tasks` to `outline tasks`, `/intuition-plan` to `/intuition-outline`, `from plan` to `from outline`.
+
+**intuition-detail**: Rename phase refs: `plan's Decisions field` to `outline's Decisions field`, `plan Section 10` to `outline Section 10`, `planning phase` to `outline phase`, `classified_by: "plan"` to `classified_by: "outline"`, `plan classifies` to `outline classifies`, `plan context` to `outline context`, `aren't in the plan` to `aren't in the outline`, `plan task's acceptance criteria` to `outline task's acceptance criteria`, `plan acceptance criterion` to `outline acceptance criterion`. KEEP all: `research-plan.md`, `Research Planning`, `research-planning framing`, `specialist planned to use`.
+
+**intuition-build**: Rename `plan.md` to `outline.md`, `plan tasks` to `outline tasks`, `plan items` to `outline items`, `plan's task definitions` to `outline's task definitions`, `plan and execution_order` to `outline and execution_order`, `plan explicitly states` to `outline explicitly states`, `plan.md acceptance criteria` to `outline.md acceptance criteria`, `classified in the plan` to `classified in the outline`. KEEP "build plan" per D2. KEEP generic comparison at line 213.
+
+**intuition-test**: Rename `plan.md` to `outline.md`, `from the plan` to `from the outline`, `from plan.md` to `from outline.md`. KEEP "test plan" per D2.
+
+**intuition-design**: Rename all `plan.md` to `outline.md`, `plan items` to `outline items`, `plan flagged` to `outline flagged`, `overall plan` to `overall outline`, `plan item triggered` to `outline item triggered`, `constraints from the plan` to `constraints from the outline`, `Plan Reference` to `Outline Reference`, `Constraints from plan` to `Constraints from outline`.
+
+**intuition-engineer**: Rename all `plan.md` to `outline.md`, `approved plan` to `approved outline`, `/intuition-plan` to `/intuition-outline`, `plan Task #[N]` to `outline Task #[N]`, `from the plan` to `from the outline`, `Planning Context for Engineer` to `Outline Context for Engineer`, `Planning Context section` to `Outline Context section`, `plan left an explicit` to `outline left an explicit`.
+
+**intuition-debugger**: Rename `plan.md` to `outline.md`, `root cause is in the plan` to `root cause is in the outline`, `workflow planning artifacts` to `workflow outline artifacts`, `plans` (context artifact) to `outlines`, `the plan was wrong` to `the outline was wrong`, `plan diverged` to `outline diverged`, `what was planned` to `what was outlined`, `does code match plan` to `does code match outline`, `plan specified` to `outline specified`, `plan went wrong` to `outline went wrong`.
+
+**intuition-handoff**: Rename all `plan.md` to `outline.md`, `planning_brief.md` to `outline_brief.md`, `workflow.planning.*` to `workflow.outline.*`, `status == "planning"` to `status == "outline"`, `"planning"` (in status enum) to `"outline"`, `plan_tasks` to `outline_tasks`, `Generate Planning Brief` to `Generate Outline Brief`, `planning completes` to `outline completes`, `prompt->planning` to `prompt->outline`, `constraints from planning` to `constraints from outlining`, `v9 plan detected` to `v9 outline detected`, `Plan Context` to `Outline Context`, `/intuition-plan` to `/intuition-outline`.
+
+### T7: Update documentation and memory
+
+Process each file with disambiguation applied:
+
+**docs/v9/decision-framework-direction.md**: Rename 5 phase refs. KEEP "research planning" at line 96.
+
+**docs/v9/decision-framework-implementation.md**: Rename all 7 refs (clean phase-name refs throughout).
+
+**docs/v9/domain-adaptive-team-architecture.md**: Rename 11 refs including "Layer 2: Plan" to "Layer 2: Outline" per D5.
+
+**ARCHITECTURE_OVERVIEW.txt**: Rename 19 refs. KEEP "Waldo doesn't plan" at line 282.
+
+**README.md**: Rename all 10 refs.
+
+**TESTING_README.md**: Rename all 7 refs.
+
+**TESTING_SUMMARY.md**: Rename all 25 refs.
+
+**MEMORY.md**: Apply disambiguation line-by-line. Key patterns:
+- RENAME: `/intuition-plan`, `plan.md`, `planning_brief.md`, `.planning_research/`, "planning phase", `"planning"` (JSON key), "plan→", "Plan →" (flow arrows), "plan skill", state schema "planning" field refs
+- KEEP: "ARCH planning", "research plan", "action plan", "build plan" (if generic)
+- Update version references: state schema to v8.0, any mention of the plan skill name