@tgoodington/intuition 11.4.0 → 11.5.1

package/docs/project_notes/archive/trunk-v9.2-complete/blueprints/technical-writer.md

@@ -1,788 +0,0 @@
-# Technical Writer Blueprint
-
-> Specialist: technical-writer
-> Tasks: T2 (Rename outline skill), T4 (Initialize state template), T5 (Update all other skills), T7 (Documentation and memory)
-> Decision Policy: aggressive (fully delegated)
-> Generated: 2026-03-04
-
----
-
-## 1. Task Reference
-
-### T2: Rename and update the outline skill (Standard)
-- **Acceptance Criteria**:
-  1. Folder exists at `skills/intuition-outline/SKILL.md` with no `skills/intuition-plan/` remaining
-  2. Zero "plan" phase-name references within the outline skill's SKILL.md
-  3. All output file paths reference `outline.md`, `outline_brief.md`, `.outline_research/`
-  4. YAML frontmatter `name` field updated to `intuition-outline`
-- **Dependencies**: T1 (audit hit list must exist first)
-
-### T4: Update initialize skill state template (Light)
-- **Acceptance Criteria**:
-  1. State template version is 8.0
-  2. Template uses `outline` field instead of `planning`
-  3. All sub-fields (started, completed, approved, etc.) preserved unchanged
-- **Dependencies**: T3 (handoff migration handler must be in place)
-
-### T5: Update all other skills (Standard)
-- **Acceptance Criteria**:
-  1. Zero "plan" phase-name references across all 9 skills
-  2. All routing messages reference `/intuition-outline`
-  3. All file paths reference `outline.md`, `outline_brief.md`
-  4. Generic English uses of "plan" (research plan, action plan, etc.) are preserved
-  5. Mode detection in start skill correctly identifies outline phase
-- **Dependencies**: T1 (audit hit list)
-
-### T7: Update documentation and memory (Standard)
-- **Acceptance Criteria**:
-  1. docs/v9/ design documents use "outline" for all phase-name references
-  2. MEMORY.md uses "outline" for all phase-name references
-  3. Root-level docs (ARCHITECTURE_OVERVIEW.txt, etc.) use "outline" for phase references
-  4. Generic English uses of "plan" preserved throughout
-  5. Version references updated (e.g., state schema v8.0)
-- **Dependencies**: T1 (audit hit list)
-
----
-
-## 2. Research Findings
-
-### Skill Files (confirmed via Stage 1 codebase reads)
-
-**`skills/intuition-plan/SKILL.md`** (~560 lines, the core rename target):
-- YAML frontmatter: `name: intuition-plan` and description field (description has no literal "plan" word -- no change needed per D1)
-- ~78 lines requiring rename across 5 categories: output file paths (~20), phase-name references (~25), artifact references (~25), section/heading names (~6), YAML frontmatter (2)
-- 1 KEEP item: line 14, a generic file path reference unrelated to phase naming
-- Named sections requiring rename: "PLAN.MD OUTPUT FORMAT", "Planning Context for Engineer", "Planning Depth Tier"
-
-**`skills/intuition-initialize/SKILL.md`**:
-- Line 137 area: `"planning"` key in state template JSON
-- Version string: `"7.0"` in template
-- All sub-fields (started, completed, completed_at, approved) are structurally unchanged
-
-**Remaining 9 Skills** (per-file RENAME/KEEP counts from Stage 1):
-
-| Skill File | Path | RENAME | KEEP | Notable Disambiguation |
-|------------|------|--------|------|------------------------|
-| intuition-start | `skills/intuition-start/SKILL.md` | 9 | 0 | State field refs: `workflow.planning.*`, status enum "planning" |
-| intuition-prompt | `skills/intuition-prompt/SKILL.md` | 10 | 1 | "plan against" at line 114 is generic English |
-| intuition-assemble | `skills/intuition-assemble/SKILL.md` | 12 | 0 | `plan.md` artifact refs, `/intuition-plan` routing |
-| intuition-detail | `skills/intuition-detail/SKILL.md` | 25 | 1 | `research-plan.md`, "Research Planning", "research-planning framing" are ALL KEEP. `classified_by: "plan"` IS RENAME. |
-| intuition-build | `skills/intuition-build/SKILL.md` | 15 | 1 | "build plan" is KEEP per D2 |
-| intuition-test | `skills/intuition-test/SKILL.md` | 12 | 0 | "test plan" is KEEP per D2 |
-| intuition-design | `skills/intuition-design/SKILL.md` | 11 | 0 | Deprecated [v8 compat] skill |
-| intuition-engineer | `skills/intuition-engineer/SKILL.md` | 22 | 0 | "Planning Context for Engineer" section name must rename |
-| intuition-debugger | `skills/intuition-debugger/SKILL.md` | 14 | 0 | "plan diverged from intent" confirmed RENAME per devops-infrastructure A3 |
-| intuition-handoff | `skills/intuition-handoff/SKILL.md` | 48 | 0 | Heaviest file; state schema, transitions, mode detection |
-
-**Total across 10 skills (excluding plan itself):** ~178 RENAME, ~3 KEEP
-
-### Documentation Files (confirmed via Stage 1 reads)
-
-| File | Path | RENAME | KEEP | Notable |
-|------|------|--------|------|---------|
-| Decision Framework Direction | `docs/v9/decision-framework-direction.md` | 5 | 1 | "research planning" at line 96 is KEEP |
-| Decision Framework Implementation | `docs/v9/decision-framework-implementation.md` | 7 | 0 | Clean phase-name refs |
-| Domain Adaptive Team Architecture | `docs/v9/domain-adaptive-team-architecture.md` | 11 | 0 | "Layer 2: Plan" becomes "Layer 2: Outline" per D5 |
-| Architecture Overview | `ARCHITECTURE_OVERVIEW.txt` | 19 | 1 | "Waldo doesn't plan" at line 282 is KEEP |
-| README | `README.md` | 10 | 0 | |
-| Testing README | `TESTING_README.md` | 7 | 0 | |
-| Testing Summary | `TESTING_SUMMARY.md` | 25 | 0 | |
-| Memory | `MEMORY.md` | ~30+ | ~5 | Heaviest doc file; high disambiguation density |
-
-### Style Conventions (confirmed from existing files)
-
-- SKILL.md files use second-person imperative ("You MUST", "NEVER", "ALWAYS")
-- Documentation files use standard technical prose
-- MEMORY.md uses terse bullet-point style with inline code formatting
-- State template uses standard JSON with string values
-- All file paths in skills use forward slashes and relative paths from project context
-
----
-
-## 3. Approach
-
-### Strategy
-
-This is a pure rename refactor with zero behavioral changes. The technical-writer scope covers four tasks:
-
-1. **T2 -- Core skill rename**: Rename the `skills/intuition-plan/` folder to `skills/intuition-outline/` and apply comprehensive text replacements within the SKILL.md file. This is the single highest-density file with ~78 rename targets.
-
-2. **T4 -- Initialize template**: A surgical 2-field change to the state template JSON in the initialize skill. The `"planning"` key becomes `"outline"` and the version increments to `"8.0"`.
-
-3. **T5 -- Other skills (9 files)**: Apply the same rename discipline across all remaining skills with per-file disambiguation guidance. The detail skill requires the most care due to its "research plan" terminology that must be preserved.
-
-4. **T7 -- Documentation and memory**: Update 8 documentation files with the same phase-name rename, preserving generic English uses. MEMORY.md has the highest disambiguation density and requires line-by-line classification.
-
-### Execution Principles
-
-- **Bulk-then-targeted**: For each file, apply safe global replacements first (artifact filenames, slash commands), then do context-sensitive targeted replacements for prose phrases.
-- **Disambiguation is authoritative**: The RENAME/KEEP classification from Stage 1 research is the single source of truth. The T1 audit hit list (produced by devops-infrastructure) provides additional cross-reference.
-- **Producer/consumer pairs must match**: When a section heading is renamed in one skill (e.g., "Planning Context for Engineer" in the outline skill), the consuming skill (engineer) must rename its reference simultaneously.
-- **No rewording beyond the rename**: This blueprint specifies exact replacement strings. No creative rewording, no style improvements, no behavioral changes.
-
----
-
-## 4. Decisions Made
-
-### A1: Detail skill "research plan" terminology is generic English
-- **Status**: Accepted (user confirmed default)
-- **Default applied**: All instances of "research plan", "research-plan.md", "Research Planning", "research-planning framing" in `skills/intuition-detail/SKILL.md` are KEPT unchanged.
-- **Rationale**: These describe the activity of planning research (Stage 1a sub-stage naming), 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.
-- **Alternatives rejected**: Renaming to "research outline" would damage the three-sub-stage naming convention and misrepresent the artifact's purpose.
-
-### A2: Named section headings rename alongside the file
-- **Status**: Accepted (user confirmed default)
-- **Default applied**: "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 must track. Consumer skills (engineer, design) must update their references simultaneously.
-- **Alternatives rejected**: Leaving headings unchanged would create a mismatch between the artifact filename and its internal section names.
-
-### A3: MEMORY.md gets same disambiguation treatment as other docs
-- **Status**: Accepted (user confirmed default)
-- **Default applied**: 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 would be actively confusing.
-- **Alternatives rejected**: Exempting MEMORY.md would leave the most-read file inconsistent with the rest of the codebase.
-
-### A4: Deprecated skills receive full rename, deprecation notices unchanged
-- **Status**: Accepted (user confirmed default)
-- **Default applied**: All phase-name references inside deprecated skills (design, engineer) are renamed identically to active skills. The `[v8 compat]` deprecation notices are not modified.
-- **Rationale**: Even deprecated code should be internally consistent. The deprecation notices do not mention the plan phase by name, so no change is needed there.
-- **Alternatives rejected**: Skipping deprecated skills would leave inconsistent artifact references if someone invokes them.
-
-### D1: YAML frontmatter description rewording for intuition-outline
-- **Tier**: SPEC (classified by outline phase)
-- **Chosen**: Leave description unchanged (minimal)
-- **Options considered**: (A) Minimal -- change only `name: intuition-outline`, leave description as-is. (B) Light reword to mention "outline". (C) Full rewrite centered on "outline" terminology.
-- **Why A was chosen**: The current description does not contain the word "plan" and accurately describes the skill's behavior. The name field change is sufficient.
-- **Why B and C were rejected**: Unnecessary rewording risks introducing inaccuracy for zero functional benefit.
-
-### D2: Treatment of compound terms "build plan" and "test plan"
-- **Tier**: SPEC (classified by detail phase)
-- **Chosen**: Leave as-is
-- **Options considered**: (A) Leave as-is -- standard English compound nouns. (B) Reword to "build strategy" / "test strategy". (C) Reword to "build sequence" / "test approach".
-- **Why A was chosen**: "Build plan" and "test plan" are established software engineering terms meaning execution strategies. No reader would confuse "test plan" with the outline.md artifact. The disambiguation rule explicitly says generic English "plan" stays.
-- **Why B and C were rejected**: Introduces unnecessary churn. "Test plan" is universally understood; alternatives are slightly less clear.
-
-### D3: Treatment of `classified_by: "plan"` metadata in detail skill
-- **Tier**: SILENT (classified by detail phase)
-- **Chosen**: Rename to `classified_by: "outline"`
-- **Options considered**: (A) Rename to track the phase rename. (B) Leave as `classified_by: "plan"` since it is stored metadata.
-- **Why A was chosen**: This is a phase-name reference embedded in metadata. It means "this decision was classified by the outline phase." Consistency requires renaming it.
-- **Why B was rejected**: Would leave mismatched terminology in metadata that is displayed to users during the decision gate.
-
-### D4: Whether deprecated skills need deprecation notice updates
-- **Tier**: SPEC (classified by outline phase)
-- **Chosen**: No change to deprecation notices
-- **Options considered**: (A) No change. (B) Add "formerly /intuition-plan, now /intuition-outline" note.
-- **Why A was chosen**: Existing deprecation notices say `[v8 compat]` and reference the v9 workflow without naming `/intuition-plan` specifically.
-- **Why B was rejected**: Unnecessary clutter in already-deprecated code with extremely low impact.
-
-### D5: Treatment of "Layer 2: Plan" in design doc
-- **Tier**: SILENT (classified by outline phase)
-- **Chosen**: Rename to "Layer 2: Outline"
-- **Options considered**: (A) Rename. (B) Keep as "Layer 2: Plan" since it is a conceptual layer name.
-- **Why A was chosen**: The known research disambiguation guidance explicitly flags this: "Layer 2: Plan is a conceptual layer name -- should become Layer 2: Outline." The layer name tracks the phase name.
-- **Why B was rejected**: Would leave the design doc inconsistent with all other phase-name references.
-
----
-
-## 5. Deliverable Specification
-
-### Documentation Architecture
-
-All changes are edits to existing files. No new files are created by T2, T4, T5, or T7.
-
-**T2 structural change**: The folder `skills/intuition-plan/` is renamed to `skills/intuition-outline/`. The file within it (`SKILL.md`) retains its name.
-
-**Files modified by task**:
-
-| Task | File | Absolute Path |
-|------|------|--------------|
-| T2 | Outline skill | `skills/intuition-outline/SKILL.md` (after folder rename) |
-| T4 | Initialize skill | `skills/intuition-initialize/SKILL.md` |
-| T5 | Start skill | `skills/intuition-start/SKILL.md` |
-| T5 | Prompt skill | `skills/intuition-prompt/SKILL.md` |
-| T5 | Assemble skill | `skills/intuition-assemble/SKILL.md` |
-| T5 | Detail skill | `skills/intuition-detail/SKILL.md` |
-| T5 | Build skill | `skills/intuition-build/SKILL.md` |
-| T5 | Test skill | `skills/intuition-test/SKILL.md` |
-| T5 | Design skill | `skills/intuition-design/SKILL.md` |
-| T5 | Engineer skill | `skills/intuition-engineer/SKILL.md` |
-| T5 | Debugger skill | `skills/intuition-debugger/SKILL.md` |
-| T5 | Handoff skill | `skills/intuition-handoff/SKILL.md` |
-| T7 | Decision Framework Direction | `docs/v9/decision-framework-direction.md` |
-| T7 | Decision Framework Implementation | `docs/v9/decision-framework-implementation.md` |
-| T7 | Domain Adaptive Team Architecture | `docs/v9/domain-adaptive-team-architecture.md` |
-| T7 | Architecture Overview | `ARCHITECTURE_OVERVIEW.txt` |
-| T7 | README | `README.md` |
-| T7 | Testing README | `TESTING_README.md` |
-| T7 | Testing Summary | `TESTING_SUMMARY.md` |
-| T7 | Memory | `MEMORY.md` |
-
-### Content Structure
-
-#### T2: `skills/intuition-outline/SKILL.md`
-
-**Step 1 -- Folder rename**: `skills/intuition-plan/` to `skills/intuition-outline/`
-
-**Step 2 -- YAML frontmatter**:
-- Change: `name: intuition-plan` to `name: intuition-outline`
-- No change to description field (per D1)
-
-**Step 3 -- Safe global replacements** (apply in this order to avoid partial matches):
-1. `planning_brief.md` to `outline_brief.md` (all instances)
-2. `.planning_research/` to `.outline_research/` (all instances with trailing slash)
-3. `.planning_research` to `.outline_research` (catch instances without trailing slash)
-4. `/intuition-plan` to `/intuition-outline` (all instances)
-5. `plan.md` to `outline.md` (all instances)
-
-**Step 4 -- Targeted replacements** (context-sensitive, match exact strings):
-
-| Old String | New String |
-|------------|-----------|
-| `PLAN.MD OUTPUT FORMAT` | `OUTLINE.MD OUTPUT FORMAT` |
-| `Planning Context for Engineer` | `Outline Context for Engineer` |
-| `Planning Depth Tier` | `Outline Depth Tier` |
-| `planning depth tier` | `outline depth tier` |
-| `planning phase` | `outline phase` |
-| `planning architect` | `outline architect` |
-| `planning is precise work` | `outlining is precise work` |
-| `final plan` | `final outline` |
-| `parent plan` | `parent outline` |
-| `draft plan` | `draft outline` |
-| `approved plan` | `approved outline` |
-| `plan-level` | `outline-level` |
-| `branch plans` | `branch outlines` |
-| `presenting the draft plan` | `presenting the draft outline` |
-| `from plan` (when artifact reference) | `from outline` |
-| `the plan` (when referring to the artifact) | `the outline` |
-
-**Step 5 -- Verify**: Zero remaining "plan" phase-name references. The only "plan" remaining should be the 1 KEEP at line 14 (generic file path reference).
-
-#### T4: `skills/intuition-initialize/SKILL.md`
-
-Two surgical changes in the state template JSON block:
-
-| Old | New |
-|-----|-----|
-| `"version": "7.0"` | `"version": "8.0"` |
-| `"planning": {` | `"outline": {` |
-
-All sub-fields within the renamed key (started, completed, completed_at, approved) remain unchanged.
-
-#### T5: Per-File Specifications
-
-##### `skills/intuition-start/SKILL.md` (9 RENAME, 0 KEEP)
-
-Global replacements:
-- `/intuition-plan` to `/intuition-outline`
-- `plan.md` to `outline.md`
-
-Targeted replacements:
-
-| Old String | New String |
-|------------|-----------|
-| `workflow.planning.started` | `workflow.outline.started` |
-| `workflow.planning.completed` | `workflow.outline.completed` |
-| `workflow.planning.approved` | `workflow.outline.approved` |
-| `workflow.planning` (any other sub-field refs) | `workflow.outline` |
-| `status == "planning"` or `status: "planning"` | `status == "outline"` or `status: "outline"` |
-| `ready_for_planning` | `ready_for_outline` |
-| `plan.md (planning done)` or similar status text | `outline.md (outline done)` |
-
-##### `skills/intuition-prompt/SKILL.md` (10 RENAME, 1 KEEP)
-
-Global replacements:
-- `/intuition-plan` to `/intuition-outline`
-
-Targeted replacements:
-
-| Old String | New String |
-|------------|-----------|
-| `planning-ready` | `outline-ready` |
-| `planning phase` | `outline phase` |
-| `Open questions for planning` | `Open questions for outlining` |
-
-**KEEP**: "plan against" at line 114 -- generic English meaning "to compare against", not a phase reference. Do NOT rename.
-
-##### `skills/intuition-assemble/SKILL.md` (12 RENAME, 0 KEEP)
-
-Global replacements:
-- `plan.md` to `outline.md`
-- `/intuition-plan` to `/intuition-outline`
-
-Targeted replacements:
-
-| Old String | New String |
-|------------|-----------|
-| `plan tasks` | `outline tasks` |
-| `from plan` | `from outline` |
-| `plan's` (possessive, when referring to the artifact) | `outline's` |
-
-##### `skills/intuition-detail/SKILL.md` (25 RENAME, 1 KEEP)
-
-**CRITICAL DISAMBIGUATION** -- This file has the highest disambiguation complexity. The builder MUST follow this classification exactly.
-
-**KEEP (do NOT rename) -- all of these**:
-- `research-plan.md` (artifact name for specialist's research plan)
-- `Research Planning` (sub-stage 1a name)
-- `research-planning framing` (sub-stage descriptor)
-- `specialist planned to use` (generic English past tense)
-- Any other instance where "plan" means "a plan for research" or "to plan research"
-
-**RENAME -- all of these**:
-
-Global replacements:
-- `plan.md` to `outline.md` (but NOT `research-plan.md` -- match must exclude "research-" prefix)
-- `/intuition-plan` to `/intuition-outline`
-
-Targeted replacements:
-
-| Old String | New String |
-|------------|-----------|
-| `plan's Decisions field` | `outline's Decisions field` |
-| `plan Section 10` | `outline Section 10` |
-| `planning phase` | `outline phase` |
-| `classified_by: "plan"` | `classified_by: "outline"` (per D3) |
-| `plan classifies` | `outline classifies` |
-| `plan context` (when meaning outline phase context) | `outline context` |
-| `aren't in the plan` | `aren't in the outline` |
-| `plan task's acceptance criteria` | `outline task's acceptance criteria` |
-| `plan acceptance criterion` | `outline acceptance criterion` |
-| `plan acceptance criteria` | `outline acceptance criteria` |
-
-**Safe disambiguation rule for `plan.md` global replacement**: Match `plan.md` only when NOT preceded by `research-`. The string `research-plan.md` must be left intact. All other `plan.md` instances are phase-name references.
-
-##### `skills/intuition-build/SKILL.md` (15 RENAME, 1 KEEP)
-
-Global replacements:
-- `plan.md` to `outline.md`
-- `/intuition-plan` to `/intuition-outline`
-
-Targeted replacements:
-
-| Old String | New String |
-|------------|-----------|
-| `plan tasks` | `outline tasks` |
-| `plan items` | `outline items` |
-| `plan's task definitions` | `outline's task definitions` |
-| `plan and execution_order` | `outline and execution_order` |
-| `plan explicitly states` | `outline explicitly states` |
-| `plan.md acceptance criteria` | `outline.md acceptance criteria` |
-| `classified in the plan` | `classified in the outline` |
-
-**KEEP**: "build plan" (all instances, lines 20, 61, 106, 109) -- per D2, these are standard English meaning "the builder's execution strategy", not a phase reference. Do NOT rename.
-
-##### `skills/intuition-test/SKILL.md` (12 RENAME, 0 KEEP)
-
-Global replacements:
-- `plan.md` to `outline.md`
-
-Targeted replacements:
-
-| Old String | New String |
-|------------|-----------|
-| `from the plan` | `from the outline` |
-| `from plan.md` | `from outline.md` |
-
-**KEEP**: "test plan" (all instances, lines 44, 102, 161, 181, 184, 197, 203) -- per D2, standard English for "testing strategy". Do NOT rename.
-
-##### `skills/intuition-design/SKILL.md` (11 RENAME, 0 KEEP)
-
-Global replacements:
-- `plan.md` to `outline.md`
-- `/intuition-plan` to `/intuition-outline`
-
-Targeted replacements:
-
-| Old String | New String |
-|------------|-----------|
-| `plan items` | `outline items` |
-| `plan flagged` | `outline flagged` |
-| `overall plan` | `overall outline` |
-| `plan item triggered` | `outline item triggered` |
-| `constraints from the plan` | `constraints from the outline` |
-| `Plan Reference` | `Outline Reference` |
-| `Constraints from plan` | `Constraints from outline` |
-
-Note: This is a deprecated `[v8 compat]` skill. Deprecation notice is NOT modified (per D4).
-
-##### `skills/intuition-engineer/SKILL.md` (22 RENAME, 0 KEEP)
-
-Global replacements:
-- `plan.md` to `outline.md`
-- `/intuition-plan` to `/intuition-outline`
-
-Targeted replacements:
-
-| Old String | New String |
-|------------|-----------|
-| `approved plan` | `approved outline` |
-| `plan Task #` (with any number) | `outline Task #` |
-| `from the plan` | `from the outline` |
-| `Planning Context for Engineer` | `Outline Context for Engineer` |
-| `Planning Context section` | `Outline Context section` |
-| `plan left an explicit` | `outline left an explicit` |
-
-Note: This is a deprecated `[v8 compat]` skill. Deprecation notice is NOT modified (per D4).
-
-##### `skills/intuition-debugger/SKILL.md` (14 RENAME, 0 KEEP)
-
-Global replacements:
-- `plan.md` to `outline.md`
-
-Targeted replacements:
-
-| Old String | New String |
-|------------|-----------|
-| `root cause is in the plan` | `root cause is in the outline` |
-| `workflow planning artifacts` | `workflow outline artifacts` |
-| `plans` (when referring to outline artifacts in context) | `outlines` |
-| `the plan was wrong` | `the outline was wrong` |
-| `plan diverged` | `outline diverged` |
-| `what was planned` | `what was outlined` |
-| `does code match plan` | `does code match outline` |
-| `plan specified` | `outline specified` |
-| `plan went wrong` | `outline went wrong` |
-
-##### `skills/intuition-handoff/SKILL.md` (48 RENAME, 0 KEEP)
-
-This is the heaviest file after the outline skill itself.
-
-Global replacements (apply in order to avoid partial matches):
-- `planning_brief.md` to `outline_brief.md`
-- `/intuition-plan` to `/intuition-outline`
-- `plan.md` to `outline.md`
-
-Targeted replacements:
-
-| Old String | New String |
-|------------|-----------|
-| `workflow.planning.started` | `workflow.outline.started` |
-| `workflow.planning.completed` | `workflow.outline.completed` |
-| `workflow.planning.approved` | `workflow.outline.approved` |
-| `workflow.planning` (any other sub-field refs) | `workflow.outline` |
-| `status == "planning"` or `status: "planning"` | `status == "outline"` or `status: "outline"` |
-| `"planning"` (in status enum definitions) | `"outline"` |
-| `plan_tasks` | `outline_tasks` |
-| `Generate Planning Brief` | `Generate Outline Brief` |
-| `planning completes` | `outline completes` |
-| `prompt->planning` or `prompt → planning` | `prompt->outline` or `prompt → outline` |
-| `constraints from planning` | `constraints from outlining` |
-| `v9 plan detected` | `v9 outline detected` |
-| `Plan Context` | `Outline Context` |
-| `"planning"` (as JSON key in state schema) | `"outline"` |
-| `planning →` (in workflow diagrams) | `outline →` |
-| `→ planning` (in workflow diagrams) | `→ outline` |
-
-#### T7: Per-File Documentation Specifications
-
-##### `docs/v9/decision-framework-direction.md` (5 RENAME, 1 KEEP)
-
-Apply phase-name renames for all instances of:
-- `plan.md`, `/intuition-plan`, `planning phase`, `plan's`, `from the plan`
-
-**KEEP**: "research planning" at line 96 -- generic English for the activity of planning research.
-
-##### `docs/v9/decision-framework-implementation.md` (7 RENAME, 0 KEEP)
-
-Clean file -- all 7 instances are phase-name references. Apply standard global and targeted replacements.
-
-##### `docs/v9/domain-adaptive-team-architecture.md` (11 RENAME, 0 KEEP)
-
-Apply standard replacements plus:
-
-| Old String | New String |
-|------------|-----------|
-| `Layer 2: Plan` | `Layer 2: Outline` (per D5) |
-
-##### `ARCHITECTURE_OVERVIEW.txt` (19 RENAME, 1 KEEP)
-
-Apply standard global and targeted replacements for all phase-name references.
-
-**KEEP**: "Waldo doesn't plan" at line 282 -- generic English describing a character's behavior, not a phase reference. Do NOT rename.
-
-##### `README.md` (10 RENAME, 0 KEEP)
-
-Clean file -- all instances are phase-name references. Apply standard replacements.
-
-##### `TESTING_README.md` (7 RENAME, 0 KEEP)
-
-Clean file. Apply standard replacements.
-
-##### `TESTING_SUMMARY.md` (25 RENAME, 0 KEEP)
-
-High density but clean -- all instances are phase-name references. Apply standard replacements.
-
-##### `MEMORY.md` (~30+ RENAME, ~5 KEEP)
-
-**CRITICAL**: This file has the highest disambiguation density of any documentation file. The builder MUST classify each instance individually.
-
-**RENAME patterns** (apply in order):
-- `planning_brief.md` to `outline_brief.md`
-- `.planning_research/` to `.outline_research/`
-- `/intuition-plan` to `/intuition-outline`
-- `plan.md` to `outline.md`
-- `"planning"` (as JSON key or state field name) to `"outline"`
-- `planning phase` to `outline phase`
-- `plan skill` to `outline skill`
-- `plan→` and `Plan →` (flow arrows) to `outline→` and `Outline →`
-- `prompt→plan` to `prompt→outline`
-- `plan→design` to `outline→design`
-- `plan→assemble` to `outline→assemble`
-- `plan detected` to `outline detected`
-- `plan context` (when meaning outline phase context) to `outline context`
-- `intuition-plan` (any remaining instances) to `intuition-outline`
-- State schema version references: update to v8.0 where the schema version is cited
-
-**KEEP patterns** (do NOT rename):
-- "ARCH planning" -- ARCH is a framework name, "planning" describes the activity
-- "research plan" -- a plan for conducting research
-- "action plan" -- generic English
-- "build plan" -- generic English (if present)
-- Any "plan" used as a generic English verb meaning "to intend" or "to strategize"
-
-### Style Guide
-
-**Voice and tone**: No change. This is a rename refactor. All existing voice and tone is preserved exactly. The builder makes only the specified string replacements and does not rephrase, reword, or restructure any content beyond the explicit replacements listed.
-
-**Terminology list**:
-
-| Context | Canonical Term | Prohibited Alternatives |
-|---------|---------------|------------------------|
-| The workflow phase | outline | plan (when meaning the phase) |
-| The output artifact file | outline.md | plan.md |
-| The skill name | intuition-outline | intuition-plan |
-| The slash command | /intuition-outline | /intuition-plan |
-| The brief file | outline_brief.md | planning_brief.md |
-| The research directory | .outline_research/ | .planning_research/ |
-| The state field | outline (JSON key) | planning (JSON key) |
-| The phase activity | outlining | planning (when meaning the phase activity) |
-| Section heading in output | "Outline Context for Engineer" | "Planning Context for Engineer" |
-| Section heading in output | "OUTLINE.MD OUTPUT FORMAT" | "PLAN.MD OUTPUT FORMAT" |
-| Section heading in output | "Outline Depth Tier" | "Planning Depth Tier" |
-
-**Preserved terms** (these are NOT prohibited -- they are correct generic English):
-- "research plan", "research-plan.md", "Research Planning", "research-planning framing"
-- "build plan", "test plan"
-- "ARCH planning"
-- "action plan"
-- "plan against" (meaning "to compare against")
-- Any use of "plan" as a generic verb meaning "to intend"
-
-### Cross-Reference Map
-
-Section heading renames that cross skill boundaries:
-
-| Heading | Producer File | Consumer File(s) | Old Name | New Name |
-|---------|--------------|-------------------|----------|----------|
-| Engineer context section | `skills/intuition-outline/SKILL.md` | `skills/intuition-engineer/SKILL.md` | "Planning Context for Engineer" | "Outline Context for Engineer" |
-| Output format heading | `skills/intuition-outline/SKILL.md` | (internal) | "PLAN.MD OUTPUT FORMAT" | "OUTLINE.MD OUTPUT FORMAT" |
-| Depth tier heading | `skills/intuition-outline/SKILL.md` | (internal) | "Planning Depth Tier" | "Outline Depth Tier" |
-
-Artifact filename renames that cross skill boundaries:
-
-| Artifact | Producer | Consumers | Old Name | New Name |
-|----------|----------|-----------|----------|----------|
-| Outline document | intuition-outline | handoff, detail, build, start, assemble, engineer, design, debugger | `outline.md` (was `plan.md`) | Already renamed |
-| Outline brief | handoff | intuition-outline | `outline_brief.md` (was `planning_brief.md`) | Already renamed |
-| Research directory | intuition-outline | (internal) | `.outline_research/` (was `.planning_research/`) | Already renamed |
-
-State field renames that cross skill boundaries:
-
-| Field | Writer | Readers | Old Key | New Key |
-|-------|--------|---------|---------|---------|
-| Workflow pipeline key | handoff, initialize | start, handoff | `"planning"` | `"outline"` |
-| Status enum value | handoff | start, handoff | `"planning"` | `"outline"` |
-
----
-
-## 6. Acceptance Mapping
-
-### T2 Acceptance Criteria
-
-| Criterion | Satisfied By |
-|-----------|-------------|
-| AC1: Folder at `skills/intuition-outline/SKILL.md`, no `skills/intuition-plan/` | Step 1 of T2 spec: folder rename from `skills/intuition-plan/` to `skills/intuition-outline/` |
-| AC2: Zero "plan" phase-name references in outline SKILL.md | Steps 3-5 of T2 spec: global replacements (5 patterns) + targeted replacements (16 patterns) + verification step |
-| AC3: All output file paths reference outline variants | Step 3 global replacements: `plan.md` to `outline.md`, `planning_brief.md` to `outline_brief.md`, `.planning_research/` to `.outline_research/` |
-| AC4: YAML frontmatter `name` updated | Step 2: `name: intuition-plan` to `name: intuition-outline` |
-
-### T4 Acceptance Criteria
-
-| Criterion | Satisfied By |
-|-----------|-------------|
-| AC1: State template version is 8.0 | T4 spec: `"version": "7.0"` to `"version": "8.0"` |
-| AC2: Template uses `outline` instead of `planning` | T4 spec: `"planning": {` to `"outline": {` |
-| AC3: All sub-fields preserved | T4 spec explicitly states all sub-fields (started, completed, completed_at, approved) remain unchanged |
-
-### T5 Acceptance Criteria
-
-| Criterion | Satisfied By |
-|-----------|-------------|
-| AC1: Zero "plan" phase-name refs across all 9 skills | Per-file specifications for all 9 skills with explicit RENAME lists totaling ~178 replacements |
-| AC2: All routing messages reference `/intuition-outline` | Global replacement `/intuition-plan` to `/intuition-outline` specified for every skill containing routing refs (start, prompt, assemble, design, engineer, handoff) |
-| AC3: All file paths reference outline variants | Global replacements for `plan.md`, `planning_brief.md`, `.planning_research/` specified for every skill |
-| AC4: Generic English preserved | KEEP lists provided for detail (research-plan.md, Research Planning, etc.), prompt ("plan against"), build ("build plan"), test ("test plan") |
-| AC5: Mode detection in start skill correct | Start skill spec: `status == "planning"` to `status == "outline"`, `workflow.planning.*` to `workflow.outline.*` |
-
-### T7 Acceptance Criteria
-
-| Criterion | Satisfied By |
-|-----------|-------------|
-| AC1: docs/v9/ design documents use "outline" | Per-file specs for decision-framework-direction.md (5 renames), decision-framework-implementation.md (7 renames), domain-adaptive-team-architecture.md (11 renames including "Layer 2: Outline") |
-| AC2: MEMORY.md uses "outline" | MEMORY.md spec with explicit RENAME patterns (~30+) and KEEP patterns (~5) |
-| AC3: Root-level docs use "outline" | Per-file specs for ARCHITECTURE_OVERVIEW.txt (19 renames, 1 KEEP), README.md (10 renames), TESTING_README.md (7 renames), TESTING_SUMMARY.md (25 renames) |
-| AC4: Generic English preserved | KEEP lists: "research planning" in decision-framework-direction.md, "Waldo doesn't plan" in ARCHITECTURE_OVERVIEW.txt, "ARCH planning" / "research plan" / "action plan" in MEMORY.md |
-| AC5: Version references updated | MEMORY.md spec includes state schema version update to v8.0 |
-
----
-
-## 7. Integration Points
-
-### Files Modified
-
-| Task | File | Change Summary |
-|------|------|---------------|
-| T2 | `skills/intuition-plan/` (folder) | Renamed to `skills/intuition-outline/` |
-| T2 | `skills/intuition-outline/SKILL.md` | ~78 text replacements (YAML frontmatter + global + targeted) |
-| T4 | `skills/intuition-initialize/SKILL.md` | 2 changes (version string + JSON key rename) |
-| T5 | `skills/intuition-start/SKILL.md` | 9 replacements |
-| T5 | `skills/intuition-prompt/SKILL.md` | 10 replacements |
-| T5 | `skills/intuition-assemble/SKILL.md` | 12 replacements |
-| T5 | `skills/intuition-detail/SKILL.md` | 25 replacements (high disambiguation) |
-| T5 | `skills/intuition-build/SKILL.md` | 15 replacements |
-| T5 | `skills/intuition-test/SKILL.md` | 12 replacements |
-| T5 | `skills/intuition-design/SKILL.md` | 11 replacements |
-| T5 | `skills/intuition-engineer/SKILL.md` | 22 replacements |
-| T5 | `skills/intuition-debugger/SKILL.md` | 14 replacements |
-| T5 | `skills/intuition-handoff/SKILL.md` | 48 replacements |
-| T7 | `docs/v9/decision-framework-direction.md` | 5 replacements |
-| T7 | `docs/v9/decision-framework-implementation.md` | 7 replacements |
-| T7 | `docs/v9/domain-adaptive-team-architecture.md` | 11 replacements |
-| T7 | `ARCHITECTURE_OVERVIEW.txt` | 19 replacements |
-| T7 | `README.md` | 10 replacements |
-| T7 | `TESTING_README.md` | 7 replacements |
-| T7 | `TESTING_SUMMARY.md` | 25 replacements |
-| T7 | `MEMORY.md` | ~30+ replacements |
-
-**Total**: ~20 files modified, ~355+ individual text replacements
-
-### Cross-Task Dependencies
-
-| This Task | Depends On | Artifact Required |
-|-----------|-----------|-------------------|
-| T2 | T1 (devops-infrastructure) | Audit hit list must exist at `docs/project_notes/trunk/audit/plan-rename-hitlist.md` for cross-reference |
-| T4 | T3 (devops-infrastructure) | Handoff v7->v8 migration handler must be in place before template version is bumped |
-| T5 | T1 (devops-infrastructure) | Audit hit list for cross-reference |
-| T7 | T1 (devops-infrastructure) | Audit hit list for cross-reference |
-| T6 (devops-infrastructure) | T2 | Folder must be renamed before install/uninstall scripts reference it |
-| T8 (devops-infrastructure) | T2, T4, T5, T7 | All content renames must be complete before verification sweep |
-
-### Producer/Consumer Section Name Coupling
-
-The following section name renames MUST be applied atomically across producer and consumer skills:
-
-1. **"Planning Context for Engineer"** -- renamed in both `skills/intuition-outline/SKILL.md` (producer, T2) and `skills/intuition-engineer/SKILL.md` (consumer, T5)
-2. **State field `"planning"`** -- renamed in `skills/intuition-initialize/SKILL.md` (template, T4), `skills/intuition-handoff/SKILL.md` (writer, T5), and `skills/intuition-start/SKILL.md` (reader, T5)
-
----
-
-## 8. Open Items
-
-| ID | Type | Description |
-|----|------|-------------|
-| V1 | [VERIFY] | At build time, confirm exact line numbers in each SKILL.md file have not shifted due to prior task edits. Use content matching (not line numbers) for all edit operations. |
-| V2 | [VERIFY] | At build time for the detail skill, verify that the `plan.md` global replacement does not inadvertently match `research-plan.md`. The builder must use a replacement strategy that excludes the `research-` prefix (e.g., match on word boundary or use negative lookbehind). |
-| V3 | [VERIFY] | At build time for MEMORY.md, verify the current content of MEMORY.md against the RENAME/KEEP classification, as MEMORY.md may have been updated between blueprint creation and build execution. |
-
-No unresolved design questions remain. All decisions recorded in Section 4.
-
----
-
-## 9. Producer Handoff
-
-### Overall Execution Order
-
-Tasks must be executed in this order due to dependencies:
-1. **T2** first (the core skill rename -- other tasks reference the renamed skill)
-2. **T4** second (initialize template -- depends on T3 being complete, which is a separate blueprint)
-3. **T5** third (other skills -- can reference the renamed folder)
-4. **T7** fourth (documentation -- last, as it describes the system that was just renamed)
-
-### T2: Rename Outline Skill
-
-- **Producer**: code-writer
-- **Output format**: Folder rename + direct file edits (Markdown/YAML)
-- **Filenames in creation order**:
-  1. Folder rename: `skills/intuition-plan/` to `skills/intuition-outline/`
-  2. Edit: `skills/intuition-outline/SKILL.md`
-- **Target change count**: ~78 text replacements
-- **Instruction tone**: Mechanical, precise. Apply global replacements first (5 patterns in specified order), then targeted replacements (16 patterns). Use content matching, not line numbers. After all replacements, verify zero remaining phase-name "plan" references (the only "plan" remaining should be the 1 KEEP item at line 14).
-
-**Content blocks in order**:
-1. Rename folder via filesystem operation
-2. Apply YAML frontmatter edit: `name: intuition-plan` to `name: intuition-outline`
-3. Apply global replacements in order: `planning_brief.md`, `.planning_research/`, `.planning_research`, `/intuition-plan`, `plan.md`
-4. Apply 16 targeted replacements per the table in Section 5
-5. Final verification scan for any remaining "plan" instances
-
-### T4: Update Initialize State Template
-
-- **Producer**: code-writer
-- **Output format**: Direct file edit (Markdown containing JSON)
-- **Filename**: `skills/intuition-initialize/SKILL.md`
-- **Target change count**: 2 edits
-- **Instruction tone**: Surgical. Two exact string replacements. Do not modify any surrounding content or sub-field structure.
-
-**Content blocks in order**:
-1. Edit version string: `"7.0"` to `"8.0"` in the state template JSON block
-2. Edit JSON key: `"planning"` to `"outline"` in the workflow object
-
-### T5: Update All Other Skills
-
-- **Producer**: code-writer
-- **Output format**: Direct file edits (Markdown)
-- **Filenames in edit order** (ordered by disambiguation complexity, simplest first):
-  1. `skills/intuition-assemble/SKILL.md` (12 renames, 0 KEEP -- clean)
-  2. `skills/intuition-test/SKILL.md` (12 renames, 0 KEEP -- clean, but "test plan" is KEEP per D2)
-  3. `skills/intuition-design/SKILL.md` (11 renames, 0 KEEP -- clean, deprecated)
-  4. `skills/intuition-start/SKILL.md` (9 renames, 0 KEEP -- state field refs)
-  5. `skills/intuition-prompt/SKILL.md` (10 renames, 1 KEEP -- "plan against")
-  6. `skills/intuition-debugger/SKILL.md` (14 renames, 0 KEEP)
-  7. `skills/intuition-build/SKILL.md` (15 renames, 1 KEEP -- "build plan" per D2)
-  8. `skills/intuition-engineer/SKILL.md` (22 renames, 0 KEEP -- section name coupling)
-  9. `skills/intuition-detail/SKILL.md` (25 renames, 1 KEEP -- highest disambiguation complexity, do last)
-  10. `skills/intuition-handoff/SKILL.md` (48 renames, 0 KEEP -- highest volume, but clean disambiguation)
-- **Target change count**: ~178 total replacements across 10 files
-- **Instruction tone**: Methodical, disciplined. For each file: read the file first, apply global replacements, then apply targeted replacements per the per-file table. For the detail skill, pay special attention to the KEEP list -- every instance of "research plan", "research-plan.md", "Research Planning", and "research-planning framing" MUST be preserved unchanged. For the build and test skills, "build plan" and "test plan" MUST be preserved per D2. Use content matching for all edits.
-
-**Content blocks per file**:
-1. Read the file
-2. Apply global replacements (artifact filenames, slash commands)
-3. Apply targeted replacements per the file's table in Section 5
-4. Verify KEEP items are still intact
-5. Move to next file
-
-### T7: Update Documentation and Memory
-
-- **Producer**: document-writer
-- **Output format**: Direct file edits (Markdown, TXT)
-- **Filenames in edit order** (ordered by disambiguation complexity, simplest first):
-  1. `docs/v9/decision-framework-implementation.md` (7 renames, 0 KEEP -- cleanest)
-  2. `README.md` (10 renames, 0 KEEP)
-  3. `TESTING_README.md` (7 renames, 0 KEEP)
-  4. `TESTING_SUMMARY.md` (25 renames, 0 KEEP)
-  5. `docs/v9/domain-adaptive-team-architecture.md` (11 renames, 0 KEEP -- includes "Layer 2" per D5)
-  6. `docs/v9/decision-framework-direction.md` (5 renames, 1 KEEP -- "research planning")
-  7. `ARCHITECTURE_OVERVIEW.txt` (19 renames, 1 KEEP -- "Waldo doesn't plan")
-  8. `MEMORY.md` (~30+ renames, ~5 KEEP -- highest disambiguation density, do last)
-- **Target change count**: ~114+ replacements across 8 files
-- **Instruction tone**: Careful, disambiguation-aware. For clean files (0 KEEP), apply global replacements confidently. For files with KEEP items, process line-by-line near the KEEP zones. For MEMORY.md, classify each "plan" instance individually using the RENAME/KEEP pattern lists in Section 5. Generic English uses of "plan" (ARCH planning, research plan, action plan, "doesn't plan") must be preserved exactly. Update state schema version references to v8.0.
-
-**Content blocks per file**:
-1. Read the file
-2. Apply global replacements for artifact filenames and slash commands
-3. Apply targeted replacements for prose phrases
-4. Verify KEEP items are still intact
-5. For MEMORY.md additionally: update state schema version references
-6. Move to next file