@tgoodington/intuition 9.2.0 → 9.2.1

package/docs/project_notes/trunk/build_brief.md

@@ -0,0 +1,119 @@
+# Build Brief
+
+> Context: trunk
+> Transition: Detail → Build (Transition 4v9)
+> Generated: 2026-03-05
+
+---
+
+## Plan Summary
+
+This project renames the `intuition-plan` skill to `intuition-outline` and updates every phase-name reference across the Intuition framework — skill files, state schema, routing messages, scripts, and documentation. The change is a pure rename refactor with zero behavioral modifications. Three specialist teams (devops-infrastructure, technical-writer, database-architect) have produced comprehensive blueprints covering all 8 tasks (T1–T8). The build phase applies these blueprints in the dependency-ordered sequence specified in team_assignment.json.
+
+The critical structural change is the state schema migration from v7.0 to v8.0 (T3, database-architect blueprint), which renames the `planning` workflow field to `outline` and adds a V7 migration handler. All other tasks are systematic text replacements with well-defined disambiguation rules established during specialist consultation.
+
+## Objective
+
+Produce a codebase with zero stale "plan" phase references, a working `/intuition-outline` skill, and a v7→v8 migration handler — without changing any behavioral logic.
+
+---
+
+## Team Summary
+
+| Specialist | Tasks | Blueprint | Producer | Output Format |
+|------------|-------|-----------|----------|---------------|
+| devops-infrastructure | T1, T6, T8 | blueprints/devops-infrastructure.md | code-writer | code (JS, JSON, Markdown report) |
+| technical-writer | T2, T4, T5, T7 | blueprints/technical-writer.md | document-writer | markdown (SKILL.md edits, docs) |
+| database-architect | T3 | blueprints/database-architect.md | code-writer | code (SKILL.md edits) |
+
+**Total**: 3 specialists, 3 blueprints, 8 tasks, ~390+ individual text replacements across ~22 files.
+
+---
+
+## Blueprint Index
+
+| Blueprint | Specialist | Tasks Covered | Producer | Key Deliverables |
+|-----------|------------|---------------|----------|-----------------|
+| devops-infrastructure.md | devops-infrastructure | T1, T6, T8 | code-writer | Audit hit list (plan-rename-hitlist.md), script/config edits (install, uninstall, package.json), verification report |
+| technical-writer.md | technical-writer | T2, T4, T5, T7 | document-writer | Folder rename (intuition-plan → intuition-outline), ~78 renames in outline skill, ~10 renames in initialize, ~178 renames across 9 other skills, ~114 renames in docs/MEMORY.md |
+| database-architect.md | database-architect | T3 | code-writer | 4 schema edits + 1 V7 handler insertion + ~21 state field renames in handoff SKILL.md |
+
+---
+
+## Execution Order
+
+**CRITICAL**: Tasks must be applied in this sequence due to file dependencies.
+
+### Phase 1 — Audit (no dependencies)
+- **T1**: Run devops-infrastructure blueprint Section 5 audit protocol. Produces `docs/project_notes/trunk/audit/plan-rename-hitlist.md`. All subsequent tasks cross-reference this hit list.
+
+### Phase 2 — Core changes (T1 must be complete; T3 and T2/T5/T7 can proceed in parallel)
+- **T3**: Apply database-architect blueprint to `skills/intuition-handoff/SKILL.md` — schema bump, V7 handler insertion, state field renames
+- **T2/T5/T7**: Apply technical-writer blueprint tasks 2, 5, 7 — rename outline skill folder, update 9 other skills, update docs
+
+### Phase 3 — Dependent changes (T3 and T2 must be complete)
+- **T4**: Apply technical-writer blueprint T4 — update initialize skill state template (depends on T3's v8 schema definition)
+- **T6**: Apply devops-infrastructure blueprint T6 — update install/uninstall scripts and package.json (depends on T2's folder rename)
+
+### Phase 4 — Verification (all prior tasks must be complete)
+- **T8**: Apply devops-infrastructure blueprint T8 — run verification sweep and produce report
+
+---
+
+## Conflict Check
+
+**Result**: Clean — No conflicts detected.
+
+All three blueprints were scanned for contradictory decisions, overlapping file modifications, inconsistent interface assumptions, and duplicated deliverables. The database-architect and technical-writer blueprints both touch `skills/intuition-handoff/SKILL.md`, but this is documented intentional overlap — both specify identical target names (`outline`) for the same strings, and the technical-writer blueprint explicitly documents which edits are unique to each blueprint.
+
+**One non-blocking execution note** (T8): The test fixture in the devops-infrastructure T8 spec uses `workflow_pipeline` and `schema_version` as field names, but the actual state schema uses `workflow` and `version`. The T8 producer should correct the fixture field names before running the migration handler test.
+
+Full conflict report: `docs/project_notes/trunk/blueprint-conflicts.md`
+
+---
+
+## Quality Gates
+
+### Security Review
+This build contains no new secrets, credentials, API keys, or authentication changes. It is a pure text rename of internal skill files and documentation. No security review required.
+
+### Domain Specialist Reviews
+- **devops-infrastructure**: Verify legacy cleanup pattern matches established fs.existsSync + fs.rmSync pattern (blueprint Section 5.3 specifies exact code block)
+- **technical-writer**: Verify disambiguation rules applied correctly — especially detail skill (research-plan.md KEPT), build/test skills (build plan/test plan KEPT), prompt skill ("plan against" KEPT)
+- **database-architect**: Verify V3 migration handler left unchanged; verify V7 handler uses `workflow.planning` → `workflow.outline` key rename with all sub-fields preserved (started, completed, completed_at, approved)
+
+### Cross-Cutting Review
+After all tasks complete, run T8 verification sweep. T8 verifies:
+1. Zero stale phase-name "plan" references in codebase
+2. `skills/intuition-outline/SKILL.md` exists with correct frontmatter
+3. Install script contains `intuition-outline` and legacy cleanup for `intuition-plan`
+4. V7→V8 migration handler transforms sample state correctly
+5. Verification report with PASS/FAIL for every check
+
+---
+
+## Known Risks
+
+| Risk | Likelihood | Impact | Mitigation |
+|------|-----------|--------|------------|
+| Generic "plan" accidentally renamed | Medium | Low | Disambiguation rules in all blueprints; T8 spot-checks generic usage |
+| T3/T5 edits to handoff conflict | Low | Medium | Both blueprints document same target strings; apply T3 first per phase 2 ordering |
+| V3 migration handler corrupted | Low | High | Blueprint Section 5.12 explicitly preserves V3 handler; T8 verification checks handler integrity |
+| T4 template mismatches T3 schema | Low | High | T4 depends on T3; technical-writer blueprint matches database-architect blueprint's field names |
+| T8 fixture field name mismatch | Low | Low | Non-blocking; T8 producer corrects fixture field names before running test |
+| Line numbers shift between blueprint creation and build | Medium | Low | All blueprints specify "use content matching, not line numbers" |
+
+---
+
+## References
+
+| File | Purpose |
+|------|---------|
+| `docs/project_notes/trunk/plan.md` | Project plan with all task definitions and acceptance criteria |
+| `docs/project_notes/trunk/blueprints/devops-infrastructure.md` | T1, T6, T8 specifications |
+| `docs/project_notes/trunk/blueprints/technical-writer.md` | T2, T4, T5, T7 specifications |
+| `docs/project_notes/trunk/blueprints/database-architect.md` | T3 specification |
+| `docs/project_notes/trunk/team_assignment.json` | Specialist assignments, execution order, dependencies |
+| `docs/project_notes/trunk/blueprint-conflicts.md` | Conflict check report |
+| `docs/project_notes/decisions.md` | ADR-P001 (rename decision), ADR-P002 (build plan/test plan preservation) |
+| `docs/project_notes/key_facts.md` | Reference inventory, blast radius, disambiguation rules |

package/docs/project_notes/trunk/build_report.md

@@ -0,0 +1,250 @@
+# Build Report
+
+**Plan:** Rename Plan Phase to Outline
+**Date:** 2026-03-05
+**Status:** Success
+
+## Task Results
+
+### Task 1: Audit all phase-name references
+- **Domain**: code/tooling
+- **Specialist**: devops-infrastructure
+- **Producer**: code-writer (sonnet)
+- **Output**: `docs/project_notes/trunk/audit/plan-rename-hitlist.md`
+- **Status**: PASS
+
+#### Review Chain
+1. **Specialist Review** (devops-infrastructure): PASS — "Comprehensive audit covering all 7 patterns; 247 RENAME, 35 KEEP across full codebase. Two minor issues fixed (docs/v9/test/ coverage, MEMORY.md path note)."
+2. **Builder Verification**: PASS — "All 3 acceptance criteria met. Audit correctly identifies files outside T7 scope (legacy docs)."
+3. **Cross-Cutting Review**: N/A — markdown document, not code/config/script
+4. **Security Review**: N/A
+
+#### Deviations from Blueprint
+None — all blueprint specs followed as written.
+
+#### Decision Compliance
+- **[USER] decisions honored**: 0 of 0 (no USER-tier decisions)
+- **[SPEC] decisions applied**: 0 — T1 had no SPEC decisions
+- **Unanticipated decisions**: 0
+
+---
+
+### Task 2: Rename and update outline skill
+- **Domain**: code/skill-definition
+- **Specialist**: technical-writer
+- **Producer**: code-writer (sonnet)
+- **Output**: `skills/intuition-outline/SKILL.md` (folder renamed from `skills/intuition-plan/`)
+- **Status**: PASS
+
+#### Review Chain
+1. **Specialist Review** (technical-writer): PASS — "~66 replacements applied. Zero stale phase-name references. 4 generic KEEP items preserved."
+2. **Builder Verification**: PASS — "Folder renamed, YAML frontmatter updated, all output file paths reference outline variants."
+3. **Cross-Cutting Review**: N/A (mandatory reviewers not applicable to markdown skill files)
+4. **Security Review**: PASS — "No secrets, injection vectors, or path traversal issues introduced."
+
+#### Deviations from Blueprint
+None — all blueprint specs followed as written.
+
+#### Decision Compliance
+- **[SPEC] decisions applied**: 1 — D1 (leave YAML description unchanged) correctly applied
+- **Unanticipated decisions**: 0
+
+---
+
+### Task 3: Update handoff skill — v7→v8 schema + migration handler
+- **Domain**: code/skill-definition
+- **Specialist**: database-architect
+- **Producer**: code-writer (sonnet)
+- **Output**: `skills/intuition-handoff/SKILL.md`
+- **Status**: PASS
+
+#### Review Chain
+1. **Specialist Review** (database-architect): PASS — "All 25+ edits applied. V7 handler inserted correctly before V5. V3/V4/V5/V6 handlers preserved unchanged."
+2. **Builder Verification**: PASS — "Schema v8.0, migration handler fires on v7.0, all state field references use 'outline'. V3 handler correctly preserves historical file names."
+3. **Cross-Cutting Review** (security-auditor): N/A (security review covered in batched review)
+4. **Security Review**: PASS — "V7 migration handler is prose instructions, not executable code. No injection vectors. State integrity preserved."
+
+#### Deviations from Blueprint
+None — all blueprint specs followed as written.
+
+#### Decision Compliance
+- **[SILENT] decisions applied**: 3 — D1 (V3 preservation), D2 (status remap scope), D3 (simple trigger)
+- **Unanticipated decisions**: 0
+
+---
+
+### Task 4: Update initialize skill state template
+- **Domain**: code/skill-definition
+- **Specialist**: technical-writer
+- **Producer**: code-writer (sonnet)
+- **Output**: `skills/intuition-initialize/SKILL.md`
+- **Status**: PASS
+
+#### Review Chain
+1. **Specialist Review** (technical-writer): PASS — "2 surgical edits applied. Sub-fields preserved."
+2. **Builder Verification**: PASS — "Version 8.0, outline key, all sub-fields intact."
+3. **Security Review**: PASS (covered in batch)
+
+#### Deviations from Blueprint
+None.
+
+#### Decision Compliance
+- **Unanticipated decisions**: 0
+
+---
+
+### Task 5: Update all other skills (9 files + handoff verification)
+- **Domain**: code/skill-definition
+- **Specialist**: technical-writer
+- **Producer**: code-writer (sonnet)
+- **Output**: 9 SKILL.md files + handoff verification
+- **Status**: PASS
+
+#### Review Chain
+1. **Specialist Review** (technical-writer): PASS — "~120 edits across 9 files. All KEEP items preserved (test plan, build plan, plan against, research-plan.md, Research Planning)."
+2. **Builder Verification**: PASS — "Zero stale phase-name references across all 9 skills. Handoff verified clean from T3."
+3. **Security Review**: PASS (covered in batch)
+
+#### Deviations from Blueprint
+None — all blueprint specs followed as written.
+
+#### Decision Compliance
+- **[SPEC] decisions applied**: 3 — D2 (build plan/test plan kept), D4 (deprecated skill notices unchanged)
+- **[SILENT] decisions applied**: 1 — D3 (classified_by: "outline")
+- **Unanticipated decisions**: 0
+
+---
+
+### Task 6: Update scripts and package configuration
+- **Domain**: code/tooling
+- **Specialist**: devops-infrastructure
+- **Producer**: code-writer (sonnet)
+- **Output**: `scripts/install-skills.js`, `scripts/uninstall-skills.js`, `package.json`
+- **Status**: PASS
+
+#### Review Chain
+1. **Specialist Review** (devops-infrastructure): PASS — "6 edits across 3 files. Legacy cleanup block follows established pattern."
+2. **Builder Verification**: PASS — "All 4 acceptance criteria met. Legacy cleanup correctly uses fs.existsSync + fs.rmSync pattern."
+3. **Security Review**: PASS — "No command injection in legacy cleanup block. Path construction uses path.join (safe)."
+
+#### Deviations from Blueprint
+None.
+
+#### Decision Compliance
+- **[SILENT] decisions applied**: 4 — D1 (v9.1 annotation), D2 (flat array legacy), D3 (description wording), D4 (help text update)
+- **Unanticipated decisions**: 0
+
+---
+
+### Task 7: Update documentation and memory files
+- **Domain**: content/documentation
+- **Specialist**: technical-writer
+- **Producer**: document-writer (sonnet)
+- **Output**: 8 documentation files
+- **Status**: PASS
+
+#### Review Chain
+1. **Specialist Review** (technical-writer): PASS — "~118 replacements across 8 files. All KEEP items preserved (ARCH planning, research planning, Waldo doesn't plan)."
+2. **Builder Verification**: PASS — "All 5 acceptance criteria met. docs/v9/ updated, MEMORY.md updated, root docs updated, generic English preserved, version refs updated."
+3. **Security Review**: N/A — documentation files
+
+#### Deviations from Blueprint
+None.
+
+#### Decision Compliance
+- **[SILENT] decisions applied**: 1 — D5 (Layer 2: Outline)
+- **Unanticipated decisions**: 0
+
+---
+
+### Task 8: Verification sweep
+- **Domain**: code/testing
+- **Specialist**: devops-infrastructure
+- **Producer**: code-writer (sonnet)
+- **Output**: `docs/project_notes/trunk/verification/devops-infrastructure-verification.md`
+- **Status**: PASS
+
+#### Review Chain
+1. **Specialist Review** (devops-infrastructure): PASS — "34/34 checks passed. Zero in-scope stale references."
+2. **Builder Verification**: PASS — "All 5 acceptance criteria met. Grep returns zero in-scope hits, structural checks pass, migration handler correct."
+3. **Security Review**: N/A — verification report
+
+#### Deviations from Blueprint
+- T8 verification fixture field names: the build brief noted `workflow_pipeline`/`schema_version` should be corrected to `workflow`/`version`. The producer used the correct field names from the actual schema, resolving this.
+
+#### Decision Compliance
+- **Unanticipated decisions**: 0
+
+---
+
+## Files Modified
+
+### Skills (SKILL.md files)
+- `skills/intuition-outline/SKILL.md` — renamed from intuition-plan, ~66 text replacements
+- `skills/intuition-handoff/SKILL.md` — schema v8.0, V7 migration handler, ~25+ replacements
+- `skills/intuition-initialize/SKILL.md` — version 8.0, outline key (2 edits)
+- `skills/intuition-start/SKILL.md` — 9 replacements
+- `skills/intuition-prompt/SKILL.md` — 10 replacements
+- `skills/intuition-assemble/SKILL.md` — 12 replacements
+- `skills/intuition-detail/SKILL.md` — 25 replacements
+- `skills/intuition-build/SKILL.md` — 15 replacements
+- `skills/intuition-test/SKILL.md` — 12 replacements
+- `skills/intuition-design/SKILL.md` — 11 replacements
+- `skills/intuition-engineer/SKILL.md` — 22 replacements
+- `skills/intuition-debugger/SKILL.md` — 14 replacements
+
+### Skills (reference files — scope expansion)
+- `skills/intuition-start/references/start_core.md` — 24 edits
+- `skills/intuition-handoff/references/handoff_core.md` — 21 edits
+- `skills/intuition-outline/references/magellan_core.md` — 6 edits
+- `skills/intuition-initialize/references/agents_template.md` — 3 edits
+- `skills/intuition-initialize/references/claude_template.md` — 7 edits
+- `skills/intuition-initialize/references/intuition_readme_template.md` — 4 edits
+- `skills/intuition-initialize/references/state_template.json` — 2 edits (version 8.0, outline key)
+- `skills/intuition-outline/references/templates/plan_template.md` — 1 edit
+
+### Scripts
+- `scripts/install-skills.js` — skill list rename, legacy cleanup block, help text
+- `scripts/uninstall-skills.js` — active list rename, legacy entry
+
+### Package
+- `package.json` — description updated
+
+### Documentation
+- `docs/v9/decision-framework-implementation.md` — 7 replacements
+- `docs/v9/decision-framework-direction.md` — 8 replacements
+- `docs/v9/domain-adaptive-team-architecture.md` — ~15 replacements
+- `README.md` — 8 replacements
+- `TESTING_README.md` — 6 replacements
+- `TESTING_SUMMARY.md` — ~25 replacements
+- `ARCHITECTURE_OVERVIEW.txt` — ~19 replacements
+- `MEMORY.md` (auto-memory) — ~30 replacements
+
+### New files created
+- `docs/project_notes/trunk/audit/plan-rename-hitlist.md` — audit hit list
+- `docs/project_notes/trunk/verification/devops-infrastructure-verification.md` — verification report
+
+## Test Deliverables Deferred
+
+No test deliverables found in blueprints.
+
+## Issues & Resolutions
+
+| Issue | Resolution |
+|-------|-----------|
+| Reference files (`references/` subdirectories) had 39 stale references not in plan scope | User approved scope expansion; 68 edits applied across 8 reference files |
+| MEMORY.md at auto-memory path, not project root | Producer given correct absolute path; file updated successfully |
+| T3/T5 overlap on handoff SKILL.md | T3 executed first; T5 verified handoff and found zero remaining edits needed |
+| Legacy docs (SKILL_INTERACTION_GUIDE.md, WALDO_V3_*, docs/v7_*, etc.) still have stale references | Logged as out-of-scope; 13 legacy files not in plan scope. T8 verification classifies these correctly. |
+
+## Required User Steps
+
+None — all changes are applied. Run `/intuition-handoff` to complete the workflow cycle.
+
+## Summary Statistics
+
+- **Tasks**: 8/8 passed
+- **Total edits**: ~530+ across ~30 files
+- **Security review**: PASS
+- **Verification sweep**: 34/34 checks passed
+- **Out-of-scope legacy files**: 13 (documented, not blocking)

package/docs/project_notes/trunk/detail_brief.md

@@ -0,0 +1,94 @@
+# Detail Brief
+
+## Current Specialist
+- **Name**: database-architect
+- **Display Name**: Database Architect
+- **Domain**: database
+- **Profile Path**: /c/Users/tgoodington/.claude/specialists/database-architect/database-architect.specialist.md
+
+## Assigned Tasks
+
+### Task T3: Update handoff skill with v7→v8 state migration (Deep)
+- **Depth**: Deep
+- **Description**: Update the handoff skill to: (a) change the schema version from 7.0 to 8.0, (b) rename the `planning` field to `outline` in the schema definition, (c) add a v7→v8 migration handler following the pattern of existing v5→v6 and v6→v7 handlers, (d) update all transition routing messages from `/intuition-plan` to `/intuition-outline`, (e) update all references to `planning_brief.md` → `outline_brief.md`, `plan.md` → `outline.md`, and the `planning` state field → `outline`.
+- **Acceptance Criteria**:
+  1. Schema version is 8.0 in the handoff SKILL.md header and schema definition
+  2. v7→v8 migration handler exists and renames `planning` → `outline` in state objects
+  3. All transition messages route to `/intuition-outline` (not `/intuition-plan`)
+  4. All file path references use `outline_brief.md`, `outline.md`
+  5. State field references use `outline` throughout
+  6. Existing v5→v6 and v6→v7 migration handlers are preserved unchanged
+- **Dependencies**: Task 1 (T1 audit hit list)
+- **Decisions**: None pre-classified (task is fully deterministic once the schema target is known)
+- **Files**: `skills/intuition-handoff/SKILL.md`
+
+## Known Research
+
+### Discovery Summary (Section 2)
+
+- **Problem**: The planning phase is named `intuition-plan` but should be `intuition-outline`
+- **Goals**: Complete naming consistency, functional routing, clean state migration
+- **Target users**: Framework author and npm package consumers
+- **Constraints**: Pure rename — no behavioral changes; state schema bumps to v8.0; handoff owns all state writes; generic English "plan" must not be touched
+- **Key finding**: Specialists and producers contain zero phase-name references — blast radius is limited to skills, scripts, state, and docs
+
+### Technology Decisions (Section 3 — ALL LOCKED)
+
+| Decision | Choice | Rationale |
+|----------|--------|-----------|
+| Derived file naming | Base form: `outline_brief.md`, `.outline_research/`, `outline.md` | User preference; cleaner naming |
+| State schema field | `planning` → `outline` (base form) | Matches 5 of 7 existing state fields |
+| Disambiguation rule | Phase-name refs → rename; generic English → keep | Standing directive from prompt brief |
+
+### Risks Relevant to T3 (Section 8)
+
+| Risk | Likelihood | Impact | Mitigation |
+|------|-----------|--------|------------|
+| State migration breaks existing projects | Low | High | Follow existing v6→v7 handler pattern exactly; test with sample v7 state |
+| Missed phase-name reference in handoff | Medium | Medium | T1 audit hit list is the reference — use it |
+
+### Planning Context for Skill-Definition Tasks (Section 10)
+
+**Domain-Specific Considerations:**
+The disambiguation rule is the core challenge. Phase-name patterns: `/intuition-plan`, `planning phase`, `"planning"` (JSON key), `plan.md`, `planning_brief.md`, `.planning_research/`, `status == "planning"`. Generic English to preserve: "research plan," "ARCH planning," "planning context" (when referring to research context, not the phase).
+
+**Migration handler location**: The v7→v8 migration handler must be added to `skills/intuition-handoff/SKILL.md` following the exact same pattern as the existing handlers:
+- V5 STATE MIGRATION section (fires when `version == "5.0"`)
+- V6 STATE MIGRATION section (fires when `version == "6.0"`)
+
+The V8 handler should fire when `version == "7.0"`. It must rename the `planning` field to `outline` in the workflow object for trunk and every branch. Set `version: "8.0"`. Report migration. Then continue with the original transition.
+
+**Cross-task coupling**: The schema T3 defines must exactly match what T4 (initialize template update) implements. T4 depends on T3 completing first.
+
+**Handoff is 500+ lines**: It is the heaviest skill file. T3's scope covers ~48 additional phase-name renames (per technical-writer Stage 1 research) plus the new migration handler. Approach: add migration handler first, then apply the comprehensive rename passes.
+
+**Decision Policy**: Fully delegated. All decisions are `[SILENT]` — the schema target is fully specified. No user gate needed.
+
+## Prior Blueprints
+
+### devops-infrastructure.md (T1, T6, T8)
+- Path: `docs/project_notes/trunk/blueprints/devops-infrastructure.md`
+- Relevance: Confirmed existing migration handler patterns in handoff (V5, V6, V4, V3 handlers). Confirmed the test fixture for T8 verification: the v7→v8 handler will be tested against a sample state object. Blueprint Section 2 has the exact script architecture details.
+
+### technical-writer.md (T2, T4, T5, T7)
+- Path: `docs/project_notes/trunk/blueprints/technical-writer.md`
+- Relevance: Specifies all the other handoff file changes (T5 scope covers handoff's ~48 phase-name renames). T3 must handle the schema definition and migration handler; T5 handles all the prose/routing renames in the same file. The blueprint's Section 5 handoff spec lists the specific rename targets: `planning_brief.md` → `outline_brief.md`, `workflow.planning.*` → `workflow.outline.*`, status enum `"planning"` → `"outline"`, etc.
+- **IMPORTANT**: T3 and T5 both modify `skills/intuition-handoff/SKILL.md`. T3 adds the migration handler and updates the schema version/definition. T5 updates all routing and prose references. The blueprints must be read together — the build phase will apply both.
+
+## Plan Context
+
+This is a pure rename refactor — no behavioral changes. T3 is the most structurally significant change: it adds a migration handler (new code) and updates the schema definition. The migration handler must follow the exact pattern established by the existing V5, V6, V4, V3 handlers in the handoff skill. The v7→v8 migration must:
+1. Detect `version == "7.0"`
+2. For trunk and every branch: rename `workflow.planning` key to `workflow.outline`
+3. Update `status` value from `"planning"` to `"outline"` if present
+4. Set version to `"8.0"`
+5. Preserve all other fields unchanged
+6. Report migration to user
+7. Then continue with the original transition
+
+The schema definition in the STATE SCHEMA section must also update from v7.0 to v8.0 and replace `"planning"` with `"outline"`.
+
+## Detail Queue
+- [completed] DevOps Infrastructure — T1 (Light), T6 (Light), T8 (Standard)
+- [completed] Technical Writer — T2 (Standard), T4 (Light), T5 (Standard), T7 (Standard)
+- [in_progress] Database Architect — T3 (Deep)

package/docs/project_notes/trunk/plan.md

@@ -0,0 +1,182 @@
+# Plan: Rename Plan Phase to Outline
+
+## 1. Objective
+
+Rename the `intuition-plan` skill to `intuition-outline` and update every reference to "plan" as a workflow phase name across the entire Intuition framework — skills, state schema, scripts, and docs. The phase behavior stays identical; this is a pure rename refactor. Success is measured by: zero stale "plan" phase references remaining, `/intuition-outline` invoking and routing correctly, and v7→v8 state migration working cleanly.
+
+## 2. Discovery Summary
+
+- **Problem**: The planning phase is named `intuition-plan` but should be `intuition-outline`
+- **Goals**: Complete naming consistency, functional routing, clean state migration
+- **Target users**: Framework author and npm package consumers
+- **Constraints**: Pure rename — no behavioral changes; state schema bumps to v8.0; handoff owns all state writes; generic English "plan" (e.g., "research plan") must not be touched
+- **Key finding**: Specialists and producers contain zero phase-name references — blast radius is limited to skills, scripts, state, and docs
+
+## 3. Technology Decisions
+
+| Decision | Choice | Status | Rationale |
+|----------|--------|--------|-----------|
+| Derived file naming | Base form: `outline_brief.md`, `.outline_research/`, `outline.md` | Locked | User preference; cleaner naming |
+| State schema field | `planning` → `outline` (base form) | Locked | Matches 5 of 7 existing state fields (prompt, design, build, test, detail) |
+| docs/v9/ treatment | Update to reflect "outline" | Locked | Living architecture docs, not historical records |
+| Disambiguation rule | Phase-name refs → rename; generic English → keep | Locked | Standing directive from prompt brief |
+
+## 6. Task Sequence
+
+### Task 1: Audit all phase-name references
+- **Domain**: code/tooling
+- **Depth**: Light
+- **Component**: Entire codebase
+- **Description**: Run comprehensive grep across the full codebase to enumerate every file and line containing "plan" in a phase-name context. Produce a categorized hit list grouped by file, distinguishing phase-name usage from generic English. This becomes the reference checklist for all subsequent tasks.
+- **Acceptance Criteria**:
+  1. A complete hit list exists covering all files with phase-name "plan" references
+  2. Each hit is categorized as phase-name (rename) or generic English (keep)
+  3. Hit list is grouped by file for easy task-by-task tracking
+- **Dependencies**: None
+- **Files**: All files in `skills/`, `scripts/`, `docs/`, `memory/`, `package.json`, `*.txt`, `*.md` at root
+
+### Task 2: Rename and update the outline skill
+- **Domain**: code/skill-definition
+- **Depth**: Standard
+- **Component**: Outline skill (formerly plan skill)
+- **Description**: Rename the `skills/intuition-plan/` folder to `skills/intuition-outline/`. Update all self-references within the SKILL.md — skill name, description, output file paths (`plan.md` → `outline.md`, `planning_brief.md` → `outline_brief.md`, `.planning_research/` → `.outline_research/`), phase-name mentions, and any routing references.
+- **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**: Task 1
+- **Decisions**:
+  - `[SPEC]` Whether YAML frontmatter `description` field needs rewording beyond the rename — low impact, easily reversed
+- **Files**: `skills/intuition-plan/` → `skills/intuition-outline/`
+
+### Task 3: Update handoff skill with v7→v8 state migration
+- **Domain**: code/skill-definition
+- **Depth**: Deep
+- **Component**: Handoff skill + state schema
+- **Description**: Update the handoff skill to: (a) change the schema version from 7.0 to 8.0, (b) rename the `planning` field to `outline` in the schema definition, (c) add a v7→v8 migration handler following the pattern of existing v5→v6 and v6→v7 handlers, (d) update all transition routing messages from `/intuition-plan` to `/intuition-outline`, (e) update all references to `planning_brief.md` → `outline_brief.md`, `plan.md` → `outline.md`, and the `planning` state field → `outline`.
+- **Acceptance Criteria**:
+  1. Schema version is 8.0 in the handoff SKILL.md header and schema definition
+  2. v7→v8 migration handler exists and renames `planning` → `outline` in state objects
+  3. All transition messages route to `/intuition-outline` (not `/intuition-plan`)
+  4. All file path references use `outline_brief.md`, `outline.md`
+  5. State field references use `outline` throughout
+  6. Existing v5→v6 and v6→v7 migration handlers are preserved unchanged
+- **Dependencies**: Task 1
+- **Files**: `skills/intuition-handoff/SKILL.md`
+
+### Task 4: Update initialize skill state template
+- **Domain**: code/skill-definition
+- **Depth**: Light
+- **Component**: Initialize skill
+- **Description**: Update the state schema template in the initialize skill to use version 8.0 and rename the `planning` field to `outline`.
+- **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**: Task 3
+- **Files**: `skills/intuition-initialize/SKILL.md`
+
+### Task 5: Update all other skills
+- **Domain**: code/skill-definition
+- **Depth**: Standard
+- **Component**: 9 remaining skills (start, prompt, assemble, detail, build, test, design, engineer, debugger)
+- **Description**: Update every reference to the plan phase across all remaining skills. This includes: routing messages (`/intuition-plan` → `/intuition-outline`), file path references (`plan.md` → `outline.md`, `planning_brief.md` → `outline_brief.md`), phase name mentions ("planning phase" → "outline phase"), state field references (`planning` → `outline`), and mode detection logic. Apply the disambiguation rule: generic English "plan" stays.
+- **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**: Task 1
+- **Decisions**:
+  - `[SPEC]` Whether deprecated skills (design, engineer) need their `[v8 compat]` deprecation notices updated beyond the phase name — minor wording
+- **Files**: `skills/intuition-start/SKILL.md`, `skills/intuition-prompt/SKILL.md`, `skills/intuition-assemble/SKILL.md`, `skills/intuition-detail/SKILL.md`, `skills/intuition-build/SKILL.md`, `skills/intuition-test/SKILL.md`, `skills/intuition-design/SKILL.md`, `skills/intuition-engineer/SKILL.md`, `skills/intuition-debugger/SKILL.md`
+
+### Task 6: Update scripts and package configuration
+- **Domain**: code/tooling
+- **Depth**: Light
+- **Component**: Install/uninstall scripts, package.json
+- **Description**: Update skill name references in install and uninstall scripts (`intuition-plan` → `intuition-outline` in the skill list arrays). Update package.json if it references the plan skill in description or scripts. Verify the install script will correctly deploy `intuition-outline` to `~/.claude/skills/`.
+- **Acceptance Criteria**:
+  1. `scripts/install-skills.js` references `intuition-outline` (not `intuition-plan`)
+  2. `scripts/uninstall-skills.js` references `intuition-outline` (not `intuition-plan`)
+  3. `package.json` contains no "plan" phase-name references
+  4. Legacy cleanup in install script handles removal of old `intuition-plan` from `~/.claude/skills/`
+- **Dependencies**: Task 2
+- **Files**: `scripts/install-skills.js`, `scripts/uninstall-skills.js`, `package.json`
+
+### Task 7: Update documentation and memory
+- **Domain**: content/documentation
+- **Depth**: Standard
+- **Component**: docs/v9/, MEMORY.md, root-level docs
+- **Description**: Update all phase-name references in: docs/v9/ design documents, MEMORY.md, ARCHITECTURE_OVERVIEW.txt, and any other root-level documentation files. Apply the disambiguation rule carefully — these files contain heavy generic English usage of "plan" alongside phase-name usage.
+- **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**: Task 1
+- **Decisions**:
+  - `[SPEC]` Judgment calls on borderline "plan" usages in docs where phase-name vs generic English is ambiguous — document any close calls
+- **Files**: `docs/v9/`, `memory/MEMORY.md`, `ARCHITECTURE_OVERVIEW.txt`, `README.md`, `TESTING_SUMMARY.md`, `TESTING_README.md`
+
+### Task 8: Verification sweep
+- **Domain**: code/testing
+- **Depth**: Standard
+- **Component**: Entire codebase
+- **Description**: Run comprehensive grep to confirm zero stale "plan" phase-name references remain. Verify: (a) `/intuition-outline` skill folder exists and contains valid SKILL.md, (b) install script correctly lists `intuition-outline`, (c) state migration handler transforms v7 state to v8, (d) no broken cross-references between skills. Produce a verification report.
+- **Acceptance Criteria**:
+  1. Grep for phase-name "plan" patterns returns zero hits across the entire codebase
+  2. `skills/intuition-outline/SKILL.md` exists with correct frontmatter
+  3. Install script skill list includes `intuition-outline` and not `intuition-plan`
+  4. v7→v8 migration handler correctly renames `planning` → `outline` in a sample state object
+  5. Verification report documents all checks performed and results
+- **Dependencies**: Tasks 2, 3, 4, 5, 6, 7
+
+### 6.5 Detail Assessment
+
+| Task(s) | Domain | Depth | Rationale |
+|---------|--------|-------|-----------|
+| Task 1 | code/tooling | Light | Mechanical grep + categorization |
+| Task 2 | code/skill-definition | Standard | Large file with disambiguation needed, one key decision |
+| Task 3 | code/skill-definition | Deep | Most structurally significant change: migration handler, schema update, 500+ line file |
+| Task 4 | code/skill-definition | Light | Simple template field rename |
+| Task 5 | code/skill-definition | Standard | 9 files with disambiguation judgment calls |
+| Task 6 | code/tooling | Light | Mechanical list updates |
+| Task 7 | content/documentation | Standard | Heavy disambiguation required in docs with mixed "plan" usage |
+| Task 8 | code/testing | Standard | Comprehensive verification with multiple check types |
+
+## 7. Testing Strategy
+
+- **Primary method**: Grep-based verification (Task 8) — exhaustive search for stale references
+- **Migration testing**: Construct a v7.0 state JSON object and verify the migration handler produces correct v8.0 output with `outline` field
+- **Functional check**: Verify `skills/intuition-outline/SKILL.md` has valid YAML frontmatter parseable by Claude Code
+- **Install script check**: Verify `intuition-outline` appears in the skill deployment list and `intuition-plan` appears in legacy cleanup
+- **Tasks requiring tests**: Task 3 (migration handler), Task 8 (verification sweep)
+- **Critical scenarios**: (1) Fresh install deploys `intuition-outline`, (2) Existing v7 state migrates to v8, (3) No skill references stale `plan` phase name
+
+## 8. Risks & Mitigations
+
+| Risk | Likelihood | Impact | Mitigation |
+|------|-----------|--------|------------|
+| Missed phase-name reference | Medium | Medium | Task 1 audit + Task 8 verification sweep with multiple grep patterns |
+| Generic "plan" accidentally renamed | Medium | Low | Disambiguation rule enforced; Task 8 spot-checks generic usage preserved |
+| State migration breaks existing projects | Low | High | Follow existing v6→v7 handler pattern exactly; test with sample v7 state |
+| Install script misses folder rename | Low | High | Task 6 explicitly verifies deployment list; legacy cleanup for old name |
+| MEMORY.md changes confuse auto-memory loading | Low | Low | MEMORY.md is regenerated per-session; stale version self-corrects |
+
+## 10. Planning Context for Detail Phase
+
+- **Domain-Specific Considerations**:
+  - **code/skill-definition**: The disambiguation rule is the core challenge. Phase-name patterns: `/intuition-plan`, `planning phase`, `"planning"` (JSON key), `plan.md`, `planning_brief.md`, `.planning_research/`, `status == "planning"`. Generic English patterns to preserve: "research plan," "ARCH planning," "planning context" (when referring to research context, not the phase).
+  - **code/tooling**: Install script uses a data-driven skill list (single array). The rename is a one-line change per script, plus adding `intuition-plan` to legacy cleanup.
+  - **content/documentation**: docs/v9/ design documents mix phase-name and generic usage heavily. The decision framework docs reference "Layer 2: Plan" as a conceptual layer name — this should become "Layer 2: Outline."
+- **Cross-Domain Dependencies**: Task 3 (handoff migration) defines the schema that Task 4 (initialize template) must match. Task 1 (audit) produces the reference checklist used by Tasks 2-7.
+- **Sequencing Considerations**: Task 1 must complete first. Tasks 2, 3, 5, 7 can proceed in parallel after Task 1. Task 4 depends on Task 3. Task 6 depends on Task 2 (needs the renamed folder to exist). Task 8 depends on all others.
+- **Open Questions**:
+  - Whether `ARCHITECTURE_OVERVIEW.txt` and other root docs exist and contain plan phase references (audit will confirm)
+  - Exact count of borderline disambiguation cases in docs/v9/ (specialists will handle per `[SPEC]` classification)
+- **Constraints**: Handoff is the ONLY skill that writes state — migration must live there. No behavioral changes to any skill. Package must continue to install correctly.
+- **Decision Policy**: User posture is fully delegated ("Team handles" across all areas). All decisions are `[SILENT]` or `[SPEC]` — the standing directive eliminates ambiguity. The few `[SPEC]` decisions are minor wording judgment calls during disambiguation.