@tgoodington/intuition 9.2.0 → 9.2.1

package/skills/intuition-handoff/SKILL.md

@@ -21,9 +21,9 @@ These are non-negotiable. Violating any of these means the protocol has failed.
 5. You MUST generate a brief for the next agent.
 6. You MUST update `.project-memory-state.json` — you are the ONLY skill that writes to this file.
 7. You MUST NOT evaluate or critique phase outputs. Process and document, never judge.
-8. You MUST NOT skip the user profile merge step during prompt→planning transitions.
+8. You MUST NOT skip the user profile merge step during prompt→outline transitions.
 9. You MUST suggest the correct next skill after completing the transition.
-10. You MUST NOT modify prompt_brief.md, plan.md, design_spec_*.md, code_specs.md, or other phase output files — they are read-only inputs.
+10. You MUST NOT modify prompt_brief.md, outline.md, design_spec_*.md, code_specs.md, or other phase output files — they are read-only inputs.
 11. You MUST manage the design loop: track which items are designed, route to next item or to engineer when all are done.
 
 ## CONTEXT PATH RESOLUTION
@@ -45,9 +45,9 @@ Before ANY transition, resolve the active context:
 
 After resolving context_path, determine the workflow version:
 
-1. Read `{context_path}plan.md` (if it exists)
-2. IF plan contains a `### 6.5 Detail Assessment` section → **v9 mode**
-3. IF plan contains a `Design Recommendations` section OR no plan exists yet → **v8 mode**
+1. Read `{context_path}outline.md` (if it exists)
+2. IF outline contains a `### 6.5 Detail Assessment` section → **v9 mode**
+3. IF outline contains a `Design Recommendations` section OR no outline exists yet → **v8 mode**
 4. Store the detected mode for use in transition detection below.
 
 ## PROTOCOL: COMPLETE FLOW
@@ -59,7 +59,7 @@ Step 2: Detect transition type from context_workflow
 Step 3: Read phase output files from {context_path}
 Step 4: Extract insights and structure findings
 Step 5: Update shared memory files (key_facts.md, decisions.md, issues.md)
-Step 6: Merge user profile learnings (prompt→planning only)
+Step 6: Merge user profile learnings (prompt→outline only)
 Step 7: Generate brief for next agent at {context_path}
 Step 8: Update .project-memory-state.json (target active context object)
 Step 9: Report what was processed and suggest next skill
@@ -71,17 +71,17 @@ After resolving context_path, context_workflow, and mode:
 
 ```
 IF context_workflow.status == "prompt" AND workflow.prompt.completed == true
-   AND workflow.planning.started == false:
-   → TRANSITION: Prompt → Planning (Transition 1)
+   AND workflow.outline.started == false:
+   → TRANSITION: Prompt → Outline (Transition 1)
 
-IF context_workflow.status == "planning" AND workflow.planning.completed == true:
+IF context_workflow.status == "outline" AND workflow.outline.completed == true:
    IF v9 mode AND NOT (workflow.detail exists AND workflow.detail.started == true):
       IF {context_path}team_assignment.json exists:
          → TRANSITION: Assemble → Detail (Transition 2.5v9)
       ELSE:
-         → TRANSITION: Plan → Assemble (Transition 2v9)
+         → TRANSITION: Outline → Assemble (Transition 2v9)
    ELSE IF v8 mode AND workflow.design.started == false AND workflow.engineering.started == false:
-      → TRANSITION: Planning → Design (Transition 2) OR Planning → Engineer (Transition 2B)
+      → TRANSITION: Outline → Design (Transition 2) OR Outline → Engineer (Transition 2B)
 
 IF v9 mode AND context_workflow.status == "detail":
    → Check workflow.detail.specialists array
@@ -118,20 +118,20 @@ IF no clear transition detected:
    → ASK USER: "Which phase just completed?" (use AskUserQuestion)
 ```
 
-## STATE SCHEMA (v7.0)
+## STATE SCHEMA (v8.0)
 
 This is the authoritative schema for `.project-memory-state.json`:
 
 ```json
 {
   "initialized": true,
-  "version": "7.0",
+  "version": "8.0",
   "active_context": "trunk",
   "trunk": {
-    "status": "none | prompt | planning | design | engineering | building | testing | detail | complete",
+    "status": "none | prompt | outline | design | engineering | building | testing | detail | complete",
     "workflow": {
       "prompt": { "started": false, "completed": false, "started_at": null, "completed_at": null, "output_files": [] },
-      "planning": { "started": false, "completed": false, "completed_at": null, "approved": false },
+      "outline": { "started": false, "completed": false, "completed_at": null, "approved": false },
       "design": { "started": false, "completed": false, "completed_at": null, "items": [], "current_item": null },
       "engineering": { "started": false, "completed": false, "completed_at": null },
       "build": { "started": false, "completed": false, "completed_at": null },
@@ -189,6 +189,10 @@ Triggered when start routes to handoff with branch creation intent. User has pro
 5. **Write updated state**. Set `last_handoff_transition` to "branch_creation".
 6. **Route user**: "Branch **[display_name]** created. Run `/clear` then `/intuition-prompt` to define what this branch will accomplish."
 
+## V7 STATE MIGRATION
+
+Fires when handoff detects `version == "7.0"`. For trunk and every branch: rename the `planning` key to `outline` in the `workflow` object (preserving all sub-fields: started, completed, completed_at, approved), and change any `status == "planning"` to `"outline"`. Set `version: "8.0"`, preserve all other fields, write state. Report: "Migrated state from v7.0 to v8.0 (renamed planning → outline)." Then continue with the original transition.
+
 ## V5 STATE MIGRATION
 
 Fires when handoff detects `version == "5.0"`. For trunk and every branch: if `workflow.detail` does not exist, add `"detail": { "started": false, "completed": false, "completed_at": null, "team_assignment": null, "specialists": [], "current_specialist": null, "execution_phase": 1 }` after `build` in the workflow object. Also add `"test": { "started": false, "completed": false, "completed_at": null, "skipped": false }` after `build`. Set `version: "7.0"`, preserve all other fields, write state. Report: "Migrated state from v5.0 to v7.0 (added detail phase + test phase)." Then continue with the original transition.
@@ -205,7 +209,7 @@ Fires when handoff detects `version == "4.0"` OR (`execution` phase exists but n
 
 Fires when handoff detects `version == "3.0"` OR missing `active_context`. Create `docs/project_notes/trunk/`. Move existing workflow artifacts (`prompt_brief.md`, `prompt_output.json`, `planning_brief.md`, `plan.md`, `design_brief.md`, `design_spec_*.md`, `execution_brief.md`, `.planning_research/`) from `docs/project_notes/` into `trunk/` — skip missing files. Restructure state: wrap existing `status` + `workflow` into `trunk` object, add `active_context: "trunk"`, `branches: {}`, rename `execution` → `build`, add `engineering` phase, set `version: "5.0"`. Preserve `initialized`, `last_handoff`, `last_handoff_transition`. Write state. Report what was migrated and confirm v5.0 upgrade. Leave shared files (`key_facts.md`, `decisions.md`, `issues.md`, `bugs.md`) at `docs/project_notes/`.
 
-## TRANSITION 1: PROMPT → PLANNING
+## TRANSITION 1: PROMPT → OUTLINE
 
 Read `{context_path}prompt_brief.md` and `{context_path}prompt_output.json` (if exists — fall back to extracting from brief manually).
 
@@ -213,39 +217,39 @@ Read `{context_path}prompt_brief.md` and `{context_path}prompt_output.json` (if
 
 **User Profile Merge:** If `prompt_output.json` has `user_profile_learnings` AND `.claude/USER_PROFILE.json` exists: read profile, merge (null fields get new values, populated fields overwrite only if confidence "high"), save. Skip if no USER_PROFILE.json.
 
-**Generate Planning Brief:** Write `{context_path}planning_brief.md` with: Discovery Summary (1-2 paragraphs), Problem Statement, Goals & Success Criteria, Key Constraints, Architectural Context, Assumptions & Risks (with confidence levels), References (prompt_brief path, ADR numbers).
+**Generate Outline Brief:** Write `{context_path}outline_brief.md` with: Discovery Summary (1-2 paragraphs), Problem Statement, Goals & Success Criteria, Key Constraints, Architectural Context, Assumptions & Risks (with confidence levels), References (prompt_brief path, ADR numbers).
 
-Update state: set `status` to `"planning"`, mark `prompt.completed = true` with timestamp, set `planning.started = true`. Route: "Prompt output processed. Planning brief saved to `{context_path}planning_brief.md`. Run `/clear` then `/intuition-plan` to create a structured plan."
+Update state: set `status` to `"outline"`, mark `prompt.completed = true` with timestamp, set `outline.started = true`. Route: "Prompt output processed. Outline brief saved to `{context_path}outline_brief.md`. Run `/clear` then `/intuition-outline` to create a structured plan."
 
-## TRANSITION 2: PLANNING → DESIGN (Initial Setup)
+## TRANSITION 2: OUTLINE → DESIGN (Initial Setup)
 
-v8 mode only. Read `{context_path}plan.md`. Find "Design Recommendations" section — extract items flagged for design with rationale and task numbers (if no section, assess tasks yourself). Extract: decisions → `decisions.md`, risks/dependencies → include in brief, planning work → `issues.md`.
+v8 mode only. Read `{context_path}outline.md`. Find "Design Recommendations" section — extract items flagged for design with rationale and task numbers (if no section, assess tasks yourself). Extract: decisions → `decisions.md`, risks/dependencies → include in brief, outline work → `issues.md`.
 
 **Present to user** via AskUserQuestion (header: "Design Items"): list each flagged item with rationale. Options: "All recommended items need design" / "Some items — let me specify" / "None — skip design, go straight to engineering". If "Some," follow up. If "None," use Transition 2B.
 
 **Generate Design Brief:** Write `{context_path}design_brief.md` for FIRST item with: Current Item, Plan Context (1-2 paragraphs), Task Details (numbers, description, acceptance criteria, dependencies), Design Rationale, Constraints, Design Queue (all items with status), References.
 
-Update state: set `status` to `"design"`, mark `planning.completed = true` with timestamp and `approved = true`, set `design.started = true`, populate `design.items`, set `design.current_item` to first item (`"in_progress"`). Route: "Plan processed. Design brief prepared for **[First Item Name]**. Run `/clear` then `/intuition-design` to begin design exploration."
+Update state: set `status` to `"design"`, mark `outline.completed = true` with timestamp and `approved = true`, set `design.started = true`, populate `design.items`, set `design.current_item` to first item (`"in_progress"`). Route: "Outline processed. Design brief prepared for **[First Item Name]**. Run `/clear` then `/intuition-design` to begin design exploration."
 
-## TRANSITION 2B: PLANNING → ENGINEER (Skip Design)
+## TRANSITION 2B: OUTLINE → ENGINEER (Skip Design)
 
 v8 mode only. Used when user confirms NO items need design. Write `{context_path}engineering_brief.md` with: Plan Summary (1-2 paragraphs), Objective, Discovery Context, Task Summary, Known Risks, References.
 
-Update state: set `status` to `"engineering"`, mark `planning.completed = true` with timestamp and `approved = true`, set `design.started = false`, `design.completed = false`, `design.items = []`, set `engineering.started = true`. Route: "Plan processed. No design items flagged. Engineering brief saved to `{context_path}engineering_brief.md`. Run `/clear` then `/intuition-engineer` to create code specs."
+Update state: set `status` to `"engineering"`, mark `outline.completed = true` with timestamp and `approved = true`, set `design.started = false`, `design.completed = false`, `design.items = []`, set `engineering.started = true`. Route: "Outline processed. No design items flagged. Engineering brief saved to `{context_path}engineering_brief.md`. Run `/clear` then `/intuition-engineer` to create code specs."
 
-## TRANSITION 2v9: PLAN → ASSEMBLE
+## TRANSITION 2v9: OUTLINE → ASSEMBLE
 
-v9 mode only. Triggers when planning completes and the plan contains a `### 6.5 Detail Assessment` section.
+v9 mode only. Triggers when outline completes and the plan contains a `### 6.5 Detail Assessment` section.
 
 ### Protocol
 
-1. **Extract and structure** from plan.md: architectural decisions → `docs/project_notes/decisions.md`, risks/dependencies → note for brief, planning insights → `docs/project_notes/issues.md`.
-2. **Update state**: Set `status` to `"planning"`, mark `planning.completed = true` with timestamp, `approved = true`.
-3. **Route user**: "Plan processed. Run `/clear` then `/intuition-assemble` to build the specialist team and begin the detail phase."
+1. **Extract and structure** from outline.md: architectural decisions → `docs/project_notes/decisions.md`, risks/dependencies → note for brief, outline insights → `docs/project_notes/issues.md`.
+2. **Update state**: Set `status` to `"outline"`, mark `outline.completed = true` with timestamp, `approved = true`.
+3. **Route user**: "Outline processed. Run `/clear` then `/intuition-assemble` to build the specialist team and begin the detail phase."
 
 ## TRANSITION 2.5v9: ASSEMBLE → DETAIL
 
-v9 mode only. Triggers when planning is complete, `{context_path}team_assignment.json` exists, and detail has not started. This means assemble has finished and the team is ready.
+v9 mode only. Triggers when outline is complete, `{context_path}team_assignment.json` exists, and detail has not started. This means assemble has finished and the team is ready.
 
 ### Protocol
 
@@ -275,18 +279,18 @@ v9 mode only. Triggers when planning is complete, `{context_path}team_assignment
 - **Dependencies**: {from plan}
 
 ## Known Research
-{Extract from plan.md the sections relevant to THIS specialist's domain and assigned tasks:}
+{Extract from outline.md the sections relevant to THIS specialist's domain and assigned tasks:}
 {- Section 2 (Discovery Summary) — full content, always include}
 {- Section 4 (Risk Analysis) — risks relevant to this specialist's tasks}
 {- Section 7 (Architectural Decisions) — decisions touching this specialist's domain}
-{- Any other plan sections that contain research findings relevant to the assigned tasks}
-{Omit sections with no relevance to this specialist. If the plan has no research relevant to this specialist, write "No prior research overlaps with this specialist's domain."}
+{- Any other outline sections that contain research findings relevant to the assigned tasks}
+{Omit sections with no relevance to this specialist. If the outline has no research relevant to this specialist, write "No prior research overlaps with this specialist's domain."}
 
 ## Prior Blueprints
 None (first specialist in execution order)
 
-## Plan Context
-{Relevant content from plan.md Section 10, if present}
+## Outline Context
+{Relevant content from outline.md Section 10, if present}
 
 ## Detail Queue
 {All specialists with status:}
@@ -328,11 +332,11 @@ v9 mode only. Triggers when the current specialist's blueprint is complete and m
 
 5. **Generate detail brief for next specialist**: Overwrite `{context_path}/detail_brief.md` with:
    - **Current Specialist**: name, display_name, domain (from next specialist's profile)
-   - **Assigned Tasks**: task details from plan
+   - **Assigned Tasks**: task details from outline
    - **Specialist Profile Path**: absolute path to the next specialist's profile
-   - **Known Research**: same extraction as Transition 2.5v9 — plan sections relevant to this specialist's domain and tasks (Section 2 always, Sections 4/7 filtered by relevance). Omit sections with no relevance.
+   - **Known Research**: same extraction as Transition 2.5v9 — outline sections relevant to this specialist's domain and tasks (Section 2 always, Sections 4/7 filtered by relevance). Omit sections with no relevance.
    - **Prior Blueprints**: paths to ALL completed blueprints in `{context_path}/blueprints/` (the next specialist may need to reference them)
-   - **Plan Context**: section 10 content
+   - **Outline Context**: section 10 content
    - **Detail Queue**: all specialists with status (completed/in_progress/pending)
 
 6. **Update state**: Set `detail.current_specialist` to next specialist name, mark next specialist `status: "in_progress"`, `stage: "stage1"`. Update `detail.execution_phase` if advanced.
@@ -376,23 +380,23 @@ v9 mode only. Triggers when ALL specialists in `detail.specialists` have `status
 
 v8 mode only. Read `{context_path}design_spec_[completed_item].md` and current state. Extract from completed spec: decisions → `decisions.md`, key facts → `key_facts.md`, design work → `issues.md`. Find next `"pending"` item in `design.items`. If none remain, proceed to Transition 4.
 
-Overwrite `{context_path}design_brief.md` for the next item with: Current Item (name + description), Plan Context, Task Details, Design Rationale, Prior Design Context, Constraints (updated with prior decisions), Design Queue (completed/current/pending), References (plan path, completed spec paths).
+Overwrite `{context_path}design_brief.md` for the next item with: Current Item (name + description), Outline Context, Task Details, Design Rationale, Prior Design Context, Constraints (updated with prior decisions), Design Queue (completed/current/pending), References (outline path, completed spec paths).
 
 Update state: mark completed item `"completed"` with `spec_file`, mark next item `"in_progress"`, set `design.current_item`. Route: "[Previous Item] design complete. Design brief updated for **[Next Item Name]** ([N] of [total], [remaining] remaining). Run `/clear` then `/intuition-design` to continue."
 
 ## TRANSITION 4: DESIGN → ENGINEER
 
-v8 mode only. Triggers when ALL design items are `"completed"` or `"skipped"`. Read all `{context_path}design_spec_*.md` and `plan.md`. Extract from specs: decisions → `decisions.md`, key facts → `key_facts.md`, design work → `issues.md`.
+v8 mode only. Triggers when ALL design items are `"completed"` or `"skipped"`. Read all `{context_path}design_spec_*.md` and `outline.md`. Extract from specs: decisions → `decisions.md`, key facts → `key_facts.md`, design work → `issues.md`.
 
-Write `{context_path}engineering_brief.md` with: Plan Summary (1-2 paragraphs), Objective, Discovery Context, Design Specifications (list each spec; include "Engineer MUST read these specs before creating code specs for flagged tasks"), Task Summary (mark tasks with design specs), Known Risks, References (plan, discovery, design spec paths).
+Write `{context_path}engineering_brief.md` with: Outline Summary (1-2 paragraphs), Objective, Discovery Context, Design Specifications (list each spec; include "Engineer MUST read these specs before creating code specs for flagged tasks"), Task Summary (mark tasks with design specs), Known Risks, References (outline, discovery, design spec paths).
 
 Update state: set `status` to `"engineering"`, mark `design.completed = true` with timestamp, set `engineering.started = true`. Route: "All design specs processed. Engineering brief saved to `{context_path}engineering_brief.md`. Run `/clear` then `/intuition-engineer` to create code specs."
 
 ## TRANSITION 5: ENGINEER → BUILD
 
-Read `{context_path}code_specs.md` and `plan.md`. Extract: engineering decisions → `decisions.md`, implementation approach facts → `key_facts.md`.
+Read `{context_path}code_specs.md` and `outline.md`. Extract: engineering decisions → `decisions.md`, implementation approach facts → `key_facts.md`.
 
-Write `{context_path}build_brief.md` with: Plan Summary (1-2 paragraphs), Objective, Code Specs Summary (task count, key decisions — 1 line each), Required User Steps, Quality Gates (security review, tests, code review), Known Risks, References (plan, code_specs, design spec paths if any).
+Write `{context_path}build_brief.md` with: Outline Summary (1-2 paragraphs), Objective, Code Specs Summary (task count, key decisions — 1 line each), Required User Steps, Quality Gates (security review, tests, code review), Known Risks, References (outline, code_specs, design spec paths if any).
 
 Update state: set `status` to `"building"`, mark `engineering.completed = true` with timestamp, set `build.started = true`. Route: "Code specs processed. Build brief saved to `{context_path}build_brief.md`. Run `/clear` then `/intuition-build` to begin implementation."
 
@@ -423,7 +427,7 @@ v9 mode only. Triggers when build completes and `team_assignment.json` contains
 - **Output files**: [from build_report]
 
 ## Acceptance Criteria
-[For each code-writer task, extract acceptance criteria from plan.md]
+[For each code-writer task, extract acceptance criteria from outline.md]
 
 ## Decision Log References
 - Specialist decision logs: [paths to {context_path}/scratch/*-decisions.json]
@@ -495,14 +499,14 @@ All shared memory files live at `docs/project_notes/` (never context_path).
 
 - **Missing prompt_output.json**: Extract insights from prompt_brief.md manually.
 - **Poor output quality**: Process as-is. Note concerns in brief. Do NOT fix outputs.
-- **New constraints from planning**: Update key_facts.md, create ADR if architectural.
+- **New constraints from outline**: Update key_facts.md, create ADR if architectural.
 - **Interrupted handoff**: Check what's updated, continue from there, don't duplicate.
 - **Corrupted state**: Infer phase from existing files. Ask user to confirm.
 - **Design item skipped mid-loop**: Mark as `"skipped"`, proceed to next. Note in engineering brief.
-- **No Design Recommendations in plan**: Present tasks to user, ask if any need design. If none, use 2B.
-- **Plan revision after design started**: Alert user. Ask whether to continue or re-evaluate.
+- **No Design Recommendations in outline**: Present tasks to user, ask if any need design. If none, use 2B.
+- **Outline revision after design started**: Alert user. Ask whether to continue or re-evaluate.
 - **Missing code_specs.md at Transition 5**: Tell user to run `/intuition-engineer` first.
-- **v9 plan detected but no assemble run yet**: Route to `/intuition-assemble`.
+- **v9 outline detected but no assemble run yet**: Route to `/intuition-assemble`.
 - **v9 specialist dependency blueprint missing**: Skip to next eligible specialist. If none are eligible, halt and ask user.
 - **v9 conflict detection finds issues**: Present all conflicts, ask user to resolve before build. Do not auto-resolve.
 - **v9 completeness gate fails**: Report exact failures per blueprint. User must fix blueprints (re-run detail) before build.

package/skills/intuition-handoff/references/handoff_core.md

@@ -8,7 +8,7 @@ Each phase produces valuable output. Your job is to:
 1. Extract the valuable insights from that output
 2. Document them properly in project memory
 3. Prepare the next agent with fresh, relevant context
-4. Maintain the flow from discovery → planning → execution
+4. Maintain the flow from discovery → outline → execution
 
 You're the administrative glue that keeps the symphony coordinated.
 
@@ -16,7 +16,7 @@ You're the administrative glue that keeps the symphony coordinated.
 
 As part of every handoff, extract user profile learnings and update the global user profile:
 
-### Discovery → Planning Handoff (User Profile Focus)
+### Discovery → Outline Handoff (User Profile Focus)
 
 **From prompt_output.json**, extract `user_profile_learnings`:
 
@@ -75,10 +75,10 @@ When invoked, determine which transition is happening:
 
 ```
 IF workflow.discovery.completed == true
-   AND workflow.planning.started == false:
-   → TRANSITION: Discovery → Planning
+   AND workflow.outline.started == false:
+   → TRANSITION: Discovery → Outline
 
-IF workflow.planning.completed == true
+IF workflow.outline.completed == true
    AND workflow.execution.started == false:
    → TRANSITION: Planning → Execution
 
@@ -91,14 +91,14 @@ Check `.project-memory-state.json` to determine current state:
 ```json
 {
   "workflow": {
-    "status": "discovery",  // or "planning", "executing"
+    "status": "discovery",  // or "outline", "executing"
     "discovery": {
       "started": true,
       "completed": true,
       "completed_at": "2025-02-02T...",
       "output_files": ["prompt_brief.md", "prompt_output.json"]
     },
-    "planning": {
+    "outline": {
       "started": false,
       "completed": false
     }
@@ -106,7 +106,7 @@ Check `.project-memory-state.json` to determine current state:
 }
 ```
 
-## Transition 1: Discovery → Planning
+## Transition 1: Discovery → Outline
 
 ### Step 1: Read Outputs
 
@@ -241,10 +241,10 @@ Example:
 
 ### Step 4: Generate Brief for Magellan
 
-Create a brief that synthesizes discovery for planning. Structure:
+Create a brief that synthesizes discovery for outline. Structure:
 
 ```markdown
-# Planning Brief: [Problem Title]
+# Outline Brief: [Problem Title]
 
 ## Discovery Summary
 [1-2 paragraph summary of what was discovered]
@@ -268,29 +268,29 @@ Create a brief that synthesizes discovery for planning. Structure:
 
 ## Assumptions & Risks
 - Assumption: [X] - Confidence: High/Medium/Low
-- Risk: [Y] - Should be explored during planning
+- Risk: [Y] - Should be explored during outline
 
 ## References
 - Discovery Brief: docs/project_notes/prompt_brief.md
 - Relevant Decisions: ADR-001, ADR-002
 
 ## Notes for Planner
-[Any observations that might help planning]
+[Any observations that might help outline]
 ```
 
-**Store as:** `docs/project_notes/planning_brief.md`
+**Store as:** `docs/project_notes/outline_brief.md`
 
 ### Step 5: Update Workflow State
 
 ```json
 {
   "workflow": {
-    "status": "planning",
+    "status": "outline",
     "discovery": {
       "completed": true,
       "completed_at": "2025-02-02T..."
     },
-    "planning": {
+    "outline": {
       "started": true,
       "started_at": "2025-02-02T..."
     }
@@ -301,27 +301,27 @@ Create a brief that synthesizes discovery for planning. Structure:
 ### Step 6: Suggest Next Step
 
 ```
-"Discovery is now part of project memory. I've created a planning brief
-at docs/project_notes/planning_brief.md.
+"Discovery is now part of project memory. I've created an outline brief
+at docs/project_notes/outline_brief.md.
 
-Ready to create a plan? Run /intuition-plan to have Magellan synthesize
+Ready to create an outline? Run /intuition-outline to have Magellan synthesize
 this discovery into a structured approach."
 ```
 
 ---
 
-## Transition 2: Planning → Execution
+## Transition 2: Outline → Execution
 
 ### Step 1: Read Output
 
 ```
-plan.md (from Magellan)
-  └─ Structured plan with tasks, dependencies, risks
+outline.md (from Magellan)
+  └─ Structured outline with tasks, dependencies, risks
 ```
 
 ### Step 2: Extract Relevant Info
 
-From `plan.md`, identify:
+From `outline.md`, identify:
 
 **Key Task Information:**
 - Task list and structure
@@ -342,8 +342,8 @@ From `plan.md`, identify:
 ### Step 3: Update Memory Files
 
 **Update issues.md:**
-- Log the planning work
-- Link to plan.md
+- Log the outline work
+- Link to outline.md
 
 Example:
 ```markdown
@@ -352,17 +352,17 @@ Example:
 - **Status**: Planned
 - **Description**: Structured plan for implementing JWT-based user
   authentication across API and frontend
-- **Plan**: docs/project_notes/plan.md
+- **Outline**: docs/project_notes/outline.md
 - **Tasks**: 8 tasks identified, ready for execution
 ```
 
 **Update decisions.md (if needed):**
-- If planning revealed new architectural choices
-- Add ADRs for decisions made during planning
+- If outline revealed new architectural choices
+- Add ADRs for decisions made during outline
 
 **Do NOT modify:**
-- key_facts.md (facts don't change, planning doesn't discover new facts)
-- bugs.md (execution finds bugs, not planning)
+- key_facts.md (facts don't change, outline doesn't discover new facts)
+- bugs.md (execution finds bugs, not outline)
 
 ### Step 4: Generate Brief for Faraday
 
@@ -405,7 +405,7 @@ Create a brief for execution. Structure:
 [Reference to existing ADRs that matter for execution]
 
 ## References
-- Full Plan: docs/project_notes/plan.md
+- Full Outline: docs/project_notes/outline.md
 - Discovery Brief: docs/project_notes/prompt_brief.md
 - Relevant Decisions: ADR-001, ADR-002, ...
 
@@ -421,7 +421,7 @@ Create a brief for execution. Structure:
 {
   "workflow": {
     "status": "executing",
-    "planning": {
+    "outline": {
       "completed": true,
       "completed_at": "2025-02-02T..."
     },
@@ -436,7 +436,7 @@ Create a brief for execution. Structure:
 ### Step 6: Suggest Next Step
 
 ```
-"Planning is now in project memory. I've created an execution brief
+"Outline is now in project memory. I've created an execution brief
 at docs/project_notes/execution_brief.md with everything Faraday needs.
 
 Ready to execute? Run /intuition-execute to have Faraday coordinate
@@ -497,7 +497,7 @@ implementation."
 - **Status**: Completed | In Progress | Blocked
 - **Description**: [1-2 line summary]
 - **Discovery Brief**: [link] (if from discovery)
-- **Plan**: [link] (if from planning)
+- **Outline**: [link] (if from outline)
 - **URL**: [link to ticket if external]
 - **Notes**: [any relevant context]
 ```
@@ -526,12 +526,12 @@ implementation."
 4. User can request re-discovery if needed
 ```
 
-### What if planning revealed new constraints?
+### What if outline revealed new constraints?
 
 ```
 1. Update key_facts.md with new constraints
 2. Create ADR if it represents architectural choice
-3. Note in issues.md that planning revealed this
+3. Note in issues.md that outline revealed this
 4. Include in execution brief for Faraday's awareness
 ```
 
@@ -565,8 +565,8 @@ Example:
 ✓ decisions.md: Added ADR-005 on database strategy
 ✓ issues.md: Logged discovery work completed
 
-I've created planning_brief.md with everything Magellan needs.
-Ready to plan? Run /intuition-plan"
+I've created outline_brief.md with everything Magellan needs.
+Ready to outline? Run /intuition-outline"
 ```
 
 ---
@@ -575,7 +575,7 @@ Ready to plan? Run /intuition-plan"
 
 Before completing handoff:
 
-- [ ] Detected correct transition (Discovery→Planning or Planning→Execution)
+- [ ] Detected correct transition (Discovery→Outline or Outline→Execution)
 - [ ] Read all necessary output files
 - [ ] Extracted insights without losing information
 - [ ] Updated memory files with proper formatting

package/skills/intuition-initialize/SKILL.md

@@ -122,7 +122,7 @@ The state file uses the v7.0 schema:
 ```json
 {
   "initialized": true,
-  "version": "7.0",
+  "version": "8.0",
   "active_context": "trunk",
   "trunk": {
     "status": "none",
@@ -134,7 +134,7 @@ The state file uses the v7.0 schema:
         "completed_at": null,
         "output_files": []
       },
-      "planning": {
+      "outline": {
         "started": false,
         "completed": false,
         "completed_at": null,