@tgoodington/intuition 9.2.0 → 9.2.1

package/docs/project_notes/trunk/blueprints/devops-infrastructure.md

@@ -0,0 +1,514 @@
+# DevOps Infrastructure Blueprint
+
+> Specialist: devops-infrastructure
+> Tasks: T1 (Audit), T6 (Scripts + Package Config), T8 (Verification Sweep)
+> Decision Policy: aggressive
+> Generated: 2026-03-04
+
+---
+
+## 1. Task Reference
+
+### T1: Audit all phase-name references (Light)
+- **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
+- **Scope**: All files in `skills/`, `scripts/`, `docs/`, `memory/`, `package.json`, `*.txt`, `*.md` at root
+
+### T6: Update scripts and package config (Light)
+- **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**: T2 (technical-writer must complete skill content rename first)
+
+### T8: Verification sweep (Standard)
+- **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**: T2, T3, T4, T5, T6, T7 (all prior tasks must be complete)
+
+---
+
+## 2. Research Findings
+
+### Script Architecture (confirmed via file reads)
+
+**`scripts/install-skills.js`** (216 lines):
+- **Skill list array**: Lines 44-60. `'intuition-plan'` at line 48.
+- **Legacy cleanup block**: Lines 98-110. Two existing entries:
+  - `intuition-discovery` (removed in v6.0) at lines 98-103
+  - `intuition-execute` (removed in v8.0) at lines 105-110
+  - Pattern: `const oldXxxDest = path.join(claudeSkillsDir, 'skill-name'); if (fs.existsSync(oldXxxDest)) { fs.rmSync(oldXxxDest, { recursive: true, force: true }); log(...); }`
+- **Help text**: Line 188: `/intuition-plan` with description "Strategic planning (ARCH protocol + design flagging)"
+
+**`scripts/uninstall-skills.js`** (99 lines):
+- **Active skill list**: Lines 44-59. `'intuition-plan'` at line 48.
+- **Legacy entries**: Lines 60-63. Two existing entries:
+  - `intuition-execute` (v8.0) at line 61
+  - `intuition-discovery` (v6.0) at line 63
+- **Structure**: Single flat array containing both active and legacy skills, separated by comments.
+
+**`package.json`** (39 lines):
+- **Description** (line 4): Contains "prompt, plan, assemble specialist teams" -- the word "plan" here is a phase-name reference in the workflow enumeration.
+- **Keywords** (line 8): Contains "planning" -- this is generic English describing the package's purpose (the tool helps users do planning activities). NOT a phase-name reference.
+
+### CI/CD and Deployment Infrastructure
+- **Platform**: npm (postinstall/preuninstall hooks)
+- **Deployment mechanism**: `npm install -g` triggers `scripts/install-skills.js` via postinstall hook
+- **Removal mechanism**: `npm uninstall -g` triggers `scripts/uninstall-skills.js` via preuninstall hook
+- **No Docker, Kubernetes, Terraform, or cloud provider configs** -- this is a local CLI tool deployed via npm
+
+### Codebase Blast Radius Summary
+- ~177 lines across ~39 files contain "plan" references
+- ~165 instances are phase-name references requiring rename
+- ~12 instances are generic English that must be preserved
+- Specialists and producers: zero phase-name references (confirmed clean)
+
+---
+
+## 3. Approach
+
+### Strategy
+This is a pure rename refactor with zero behavioral changes. The devops-infrastructure scope covers three concerns:
+
+1. **T1 -- Audit**: Produce a comprehensive, categorized hit list of all "plan" references across the codebase using a defined set of grep patterns and disambiguation rules. This hit list serves as the authoritative work manifest for all other tasks.
+
+2. **T6 -- Script and config updates**: Apply precise, line-level edits to `install-skills.js`, `uninstall-skills.js`, and `package.json` to rename the active skill entry and add legacy cleanup/removal entries.
+
+3. **T8 -- Verification**: Execute a multi-phase verification protocol that confirms zero stale references remain, structural integrity is maintained, and migration handlers function correctly.
+
+### Infrastructure Philosophy
+- **Legacy cleanup is mandatory**: Users upgrading via `npm update` must have stale `intuition-plan` folders removed automatically. The existing pattern (fs.existsSync + fs.rmSync) is proven and must be followed exactly.
+- **Uninstall must be comprehensive**: The uninstall script must remove both the new name (active users) and the old name (partially-migrated users).
+- **Package metadata accuracy**: npm registry-facing description must reflect current phase naming. Keywords remain unchanged (generic English).
+
+---
+
+## 4. Decisions Made
+
+### A1: Legacy cleanup ordering is correct
+- **Status**: Accepted (assumption confirmed)
+- **Basis**: Stage 1 research confirmed legacy cleanup runs at lines 98-110, before skill deployment at lines 127-138. This means old `intuition-plan` will be removed before new `intuition-outline` is deployed. No ordering change needed.
+
+### A2: Package.json keywords "planning" is generic English
+- **Status**: Accepted (assumption confirmed)
+- **Basis**: The keyword "planning" at line 8 describes the package's functional purpose (it helps users plan projects). It is not a reference to the internal phase name. Compare with the description at line 4 where "plan" appears in a workflow enumeration ("prompt, plan, assemble") -- that IS a phase-name reference.
+- **Action**: Keywords array left unchanged; description updated.
+
+### A3: Debugger "plan diverged from intent" is a phase-name reference
+- **Status**: Accepted (assumption confirmed)
+- **Basis**: The debugger phrase refers to the `plan.md` output artifact diverging from user intent. Since `plan.md` is being renamed to `outline.md`, this reference must update to "outline diverged from intent."
+- **Scope note**: This change falls under T3 (technical-writer), not T6 (devops-infrastructure). Documented here for cross-task awareness.
+
+### D1: Version annotation for legacy cleanup comment
+- **Tier**: SILENT
+- **Chosen**: v9.1 annotation
+- **Alternatives considered**: (a) No version annotation, (b) v9.2 annotation matching current package.json version
+- **Rationale**: The rename refactor was designed as part of v9.1. Using v9.1 is consistent with the design decision epoch, not the release version. This matches the existing pattern where v6.0 and v8.0 annotations in the legacy cleanup block refer to the version that introduced the change.
+
+### D2: Uninstall script legacy entry placement
+- **Tier**: SILENT
+- **Chosen**: Add `'intuition-plan'` to existing legacy section in the `skillsToRemove` array
+- **Alternatives considered**: (a) Separate legacy cleanup block with conditional logic (like install script), (b) Comment-separated section
+- **Rationale**: The uninstall script uses a flat array pattern where legacy entries are appended with version comments. Adding to this existing pattern is consistent and minimal. The uninstall script does not need conditional logic because `removeDir` already handles non-existent directories gracefully (returns false).
+
+### D3: Package.json description wording
+- **Tier**: SILENT
+- **Chosen**: Replace "plan" with "outline" in the phase enumeration
+- **Alternatives considered**: (a) Rewrite entire description, (b) Remove phase enumeration entirely
+- **Rationale**: Minimal change. The description's structure "prompt, plan, assemble..." is a clear phase enumeration. Changing only the phase name to "outline" preserves the description's structure and meaning.
+
+### D4: Help text update in install script
+- **Tier**: SILENT
+- **Chosen**: Update both the skill name and the description text
+- **Alternatives considered**: (a) Update name only, keep old description, (b) Remove description entirely
+- **Rationale**: The help text at line 188 has two components: the slash command name (`/intuition-plan`) and the description ("Strategic planning (ARCH protocol + design flagging)"). The name must change to `/intuition-outline`. The description should change from "Strategic planning" to "Strategic outline" to match the rename. The parenthetical "(ARCH protocol + design flagging)" remains accurate regardless of naming.
+
+---
+
+## 5. Deliverable Specification
+
+### T1: Audit Hit List
+
+The producer must generate a markdown document containing the complete categorized hit list.
+
+#### Grep Pattern Set
+
+Run each pattern across the full codebase, excluding `node_modules/`, `.git/`, `specialists/`, `producers/`:
+
+| # | Pattern | Target |
+|---|---------|--------|
+| 1 | `intuition-plan` | Skill name references (folders, routing, slash commands) |
+| 2 | `planning_brief` | Output file name references |
+| 3 | `plan\.md` | Output artifact file references (escaped dot) |
+| 4 | `\.planning_research` | Research directory references |
+| 5 | `"planning"` | JSON key/status value references |
+| 6 | `planning phase` | Prose phase-name references (case-insensitive) |
+| 7 | `planning →\|→ planning\|→planning\|planning→` | Workflow diagram references |
+
+#### Disambiguation Rules
+
+Each hit is categorized using these rules:
+
+**RENAME** (phase-name reference) if the hit matches ANY of:
+- `/intuition-plan` (skill folder, slash command, routing target)
+- `planning_brief.md` (output artifact filename)
+- `plan.md` when referring to the plan skill's output artifact
+- `.planning_research/` (research directory)
+- `"planning"` as a JSON key or status value in state management
+- `planning phase` when referring to the workflow phase by name
+- `planning →` or `→ planning` in workflow transition diagrams
+- `status == "planning"` or equivalent status checks
+
+**KEEP** (generic English) if the hit matches ANY of:
+- "research plan" (a plan for conducting research, not the phase)
+- "ARCH planning" (ARCH is a framework name, "planning" is the activity)
+- "planning context" (when meaning research context, not the phase)
+- "action plan" (generic English phrase)
+- "continue planning" (activity verb, not phase name)
+- "planning" in `package.json` keywords array (generic functional descriptor)
+
+**BORDERLINE** handling:
+- `package.json` keywords "planning" -> KEEP (rationale: per A2, generic English)
+- `intuition-debugger/SKILL.md` "plan diverged from intent" -> RENAME (rationale: per A3, refers to `plan.md` artifact)
+
+#### Output Format
+
+Markdown table grouped by file:
+
+```markdown
+### `path/to/file.ext`
+
+| Line | Content (truncated) | Category | Notes |
+|------|---------------------|----------|-------|
+| 48   | `'intuition-plan',` | RENAME   | Skill list array entry |
+| ...  | ...                 | ...      | ...   |
+```
+
+Write to: `docs/project_notes/trunk/audit/plan-rename-hitlist.md`
+
+### T6: Script and Package Config Updates
+
+#### File 1: `scripts/install-skills.js`
+
+**Change 1 -- Skill list array (line 48)**:
+- Old: `  'intuition-plan',`
+- New: `  'intuition-outline',`
+
+**Change 2 -- Legacy cleanup block (insert after line 110, before line 112)**:
+
+Insert the following block between the existing `intuition-execute` cleanup (ending line 110) and the specialist/producer directory setup comment (line 112):
+
+```javascript
+
+  // Remove old plan skill if it exists (renamed to outline in v9.1)
+  const oldPlanDest = path.join(claudeSkillsDir, 'intuition-plan');
+  if (fs.existsSync(oldPlanDest)) {
+    fs.rmSync(oldPlanDest, { recursive: true, force: true });
+    log(`Removed old /intuition-plan skill (renamed to /intuition-outline in v9.1)`);
+  }
+```
+
+This follows the exact pattern established by `intuition-discovery` (lines 98-103) and `intuition-execute` (lines 105-110):
+1. Comment with version annotation (per D1: v9.1)
+2. `const` declaration with `path.join(claudeSkillsDir, 'old-name')`
+3. `if (fs.existsSync(...))` guard
+4. `fs.rmSync(...)` with `{ recursive: true, force: true }`
+5. `log(...)` with explanation including old and new names
+
+**Change 3 -- Help text (line 188)**:
+- Old: ``  log(`  /intuition-plan           - Strategic planning (ARCH protocol + design flagging)`);``
+- New: ``  log(`  /intuition-outline        - Strategic outline (ARCH protocol + design flagging)`);``
+
+Note: The alignment spacing changes from 11 spaces (after "plan") to 8 spaces (after "outline") to maintain column alignment with other help text entries. The dash column is at position 30 in all help text lines.
+
+#### File 2: `scripts/uninstall-skills.js`
+
+**Change 1 -- Active skill list (line 48)**:
+- Old: `    'intuition-plan',`
+- New: `    'intuition-outline',`
+
+**Change 2 -- Legacy entries (insert after line 63, before the closing `];` at line 64)**:
+
+Add `'intuition-plan'` to the legacy section. The resulting legacy section should read:
+
+```javascript
+    // Legacy skills (removed in v8.0)
+    'intuition-execute',
+    // Legacy skills (removed in v6.0)
+    'intuition-discovery',
+    // Legacy skills (renamed in v9.1)
+    'intuition-plan'
+  ];
+```
+
+Per D2: follows the existing flat-array pattern with version-annotated comments.
+
+#### File 3: `package.json`
+
+**Change 1 -- Description (line 4)**:
+- Old: `"description": "Domain-adaptive workflow system for Claude Code: prompt, plan, assemble specialist teams, detail with domain experts, build with format producers, test code output. Supports v8 compat (design, engineer, build) and v9 specialist workflows with 14 domain specialists and 6 format producers.",`
+- New: `"description": "Domain-adaptive workflow system for Claude Code: prompt, outline, assemble specialist teams, detail with domain experts, build with format producers, test code output. Supports v8 compat (design, engineer, build) and v9 specialist workflows with 14 domain specialists and 6 format producers.",`
+
+Single word change: "plan" -> "outline" in the phase enumeration (per D3).
+
+**No change to keywords**: "planning" at line 8 is generic English (per A2, D3).
+
+### T8: Verification Protocol
+
+#### Phase 1 -- Zero Stale References
+
+Re-run the exact grep pattern set from T1 across the full codebase (excluding `node_modules/`, `.git/`, `specialists/`, `producers/`):
+
+| # | Pattern | Expected Result |
+|---|---------|-----------------|
+| 1 | `intuition-plan` | Zero hits (all renamed to `intuition-outline`) |
+| 2 | `planning_brief` | Zero hits (all renamed to `outline_brief`) |
+| 3 | `plan\.md` (as output artifact) | Zero hits after filtering generic English (all renamed to `outline.md`) |
+| 4 | `\.planning_research` | Zero hits (all renamed to `.outline_research`) |
+| 5 | `"planning"` (as JSON key/status) | Zero hits after filtering generic English |
+| 6 | `planning phase` (as workflow phase name) | Zero hits after filtering generic English |
+| 7 | Workflow diagram arrows with `planning` | Zero hits |
+
+For each hit found: cross-reference against the T1 hit list. If the hit was categorized as KEEP, it is expected and passes. If it was categorized as RENAME, it indicates incomplete work -- FAIL.
+
+#### Phase 2 -- Structural Verification
+
+| Check | Command/Method | Expected |
+|-------|---------------|----------|
+| S1 | `ls skills/intuition-outline/SKILL.md` | File exists |
+| S2 | Read frontmatter of `skills/intuition-outline/SKILL.md` | Contains correct skill name |
+| S3 | `ls skills/intuition-plan/` | Directory does NOT exist |
+| S4 | Read `scripts/install-skills.js` skill list | Contains `'intuition-outline'`, does NOT contain `'intuition-plan'` |
+| S5 | Read `scripts/uninstall-skills.js` active list | Contains `'intuition-outline'`, does NOT contain active `'intuition-plan'` |
+| S6 | Read `scripts/install-skills.js` legacy block | Contains `intuition-plan` removal block |
+| S7 | Read `scripts/uninstall-skills.js` legacy section | Contains `'intuition-plan'` in legacy entries |
+
+#### Phase 3 -- Migration Handler Validation
+
+Create a minimal test JSON fixture representing a v7 state object with `"planning"` as a status value and as a pipeline key. Run the v7->v8 migration handler against it. Verify:
+- Status value `"planning"` is transformed to `"outline"`
+- Pipeline key `"planning"` is transformed to `"outline"`
+- All other fields are unchanged
+
+Test fixture:
+```json
+{
+  "schema_version": "7.0",
+  "active_context": {
+    "status": "planning",
+    "workflow_pipeline": {
+      "planning": { "status": "in_progress" }
+    }
+  }
+}
+```
+
+Expected output after migration:
+```json
+{
+  "schema_version": "8.0",
+  "active_context": {
+    "status": "outline",
+    "workflow_pipeline": {
+      "outline": { "status": "in_progress" }
+    }
+  }
+}
+```
+
+#### Phase 4 -- Cross-Reference Integrity
+
+For each skill that produces or consumes outline artifacts, verify filename consistency:
+
+| Artifact | Producer Skill | Consumer Skills | Expected Name |
+|----------|---------------|-----------------|---------------|
+| Outline document | intuition-outline | intuition-handoff, intuition-detail, intuition-build, intuition-start | `outline.md` |
+| Outline brief | intuition-handoff | intuition-outline | `outline_brief.md` |
+| Research directory | intuition-outline | (internal only) | `.outline_research/` |
+
+For each row: grep the producer skill for the artifact name, grep each consumer skill for the same name. All must match exactly.
+
+#### Output Format
+
+Write verification report to: `docs/project_notes/trunk/verification/devops-infrastructure-verification.md`
+
+Format:
+```markdown
+# DevOps Infrastructure Verification Report
+
+## Phase 1: Zero Stale References
+| Pattern | Hits Found | Expected Hits | Status |
+|---------|-----------|---------------|--------|
+| ...     | ...       | ...           | PASS/FAIL |
+
+## Phase 2: Structural Verification
+| Check | Result | Status |
+|-------|--------|--------|
+| S1    | ...    | PASS/FAIL |
+
+## Phase 3: Migration Handler
+| Test | Input | Expected | Actual | Status |
+|------|-------|----------|--------|--------|
+| ...  | ...   | ...      | ...    | PASS/FAIL |
+
+## Phase 4: Cross-Reference Integrity
+| Artifact | Producer Match | Consumer Matches | Status |
+|----------|---------------|-----------------|--------|
+| ...      | ...           | ...             | PASS/FAIL |
+
+## Summary
+- Total checks: N
+- Passed: N
+- Failed: N
+- Overall: PASS/FAIL
+```
+
+---
+
+## 6. Acceptance Mapping
+
+### T1 Acceptance Criteria
+
+| Criterion | Satisfied By |
+|-----------|-------------|
+| AC1: Complete hit list covering all files | Grep pattern set (7 patterns) run across full codebase scope. Patterns derived from Stage 1 research blast radius analysis of ~177 lines across ~39 files. |
+| AC2: Each hit categorized | Disambiguation rules (RENAME/KEEP/BORDERLINE) applied per hit with documented rationale. Rules derived from Stage 1 confirmed patterns. |
+| AC3: Hit list grouped by file | Output format specification requires markdown tables grouped by file path. |
+
+### T6 Acceptance Criteria
+
+| Criterion | Satisfied By |
+|-----------|-------------|
+| AC1: install-skills.js references `intuition-outline` | Change 1: Line 48 `'intuition-plan'` -> `'intuition-outline'` in skill list array |
+| AC2: uninstall-skills.js references `intuition-outline` | Change 1: Line 48 `'intuition-plan'` -> `'intuition-outline'` in active skill list |
+| AC3: package.json no plan phase-name refs | Change 1: Description "plan" -> "outline" in phase enumeration. Keywords "planning" preserved (generic English per A2). |
+| AC4: Legacy cleanup handles old `intuition-plan` | Change 2 in install-skills.js: New legacy cleanup block following established pattern (fs.existsSync + fs.rmSync). Change 2 in uninstall-skills.js: `'intuition-plan'` added to legacy entries. |
+
+### T8 Acceptance Criteria
+
+| Criterion | Satisfied By |
+|-----------|-------------|
+| AC1: Grep returns zero phase-name hits | Phase 1 of verification protocol: all 7 patterns re-run, cross-referenced against T1 hit list |
+| AC2: `intuition-outline/SKILL.md` exists | Phase 2 checks S1 and S2 |
+| AC3: Install script correct | Phase 2 checks S4 and S6 |
+| AC4: Migration handler correct | Phase 3: test fixture run through v7->v8 migration handler |
+| AC5: Verification report documents all | Output format specification with PASS/FAIL for every check |
+
+---
+
+## 7. Integration Points
+
+### Files Modified by T6
+
+| File | Absolute Path | Lines Affected |
+|------|--------------|----------------|
+| Install script | `scripts/install-skills.js` | Line 48 (skill list), Lines 111-116 (new legacy block, inserted), Line 188 (help text) |
+| Uninstall script | `scripts/uninstall-skills.js` | Line 48 (active list), Lines 64-65 (new legacy entry, inserted) |
+| Package manifest | `package.json` | Line 4 (description) |
+
+### Files Produced by T1
+
+| File | Path | Purpose |
+|------|------|---------|
+| Audit hit list | `docs/project_notes/trunk/audit/plan-rename-hitlist.md` | Authoritative reference for all rename tasks |
+
+### Files Produced by T8
+
+| File | Path | Purpose |
+|------|------|---------|
+| Verification report | `docs/project_notes/trunk/verification/devops-infrastructure-verification.md` | Final quality gate documentation |
+
+### Cross-Task Dependencies
+
+| This Task | Depends On | Artifact Consumed |
+|-----------|-----------|-------------------|
+| T6 | T2 (technical-writer) | Skill folder must already be renamed to `skills/intuition-outline/` before install script references it |
+| T8 | All (T1-T7) | All rename work must be complete before verification sweep can produce meaningful results |
+
+### State Schema Integration
+
+The v7->v8 state migration handler in `skills/intuition-handoff/SKILL.md` (or its reference files) must transform:
+- Status value: `"planning"` -> `"outline"`
+- Pipeline key: `"planning"` -> `"outline"`
+
+This migration handler is NOT written by T6 (devops-infrastructure). It is written by another task (likely T4 or T5). T8 verifies it works correctly.
+
+---
+
+## 8. Open Items
+
+| ID | Type | Description |
+|----|------|-------------|
+| V1 | [VERIFY] | At build time for T6, confirm the exact line numbers in `install-skills.js` and `uninstall-skills.js` have not shifted due to prior task edits. Use content matching (not line numbers) for edit operations. |
+| V2 | [VERIFY] | At build time for T8, confirm the migration handler file path. Stage 1 research indicates it is in `skills/intuition-handoff/SKILL.md` or `skills/intuition-handoff/references/handoff_core.md`. The verification protocol must locate the actual handler before testing. |
+| V3 | [VERIFY] | At build time for T6 help text change, verify column alignment against surrounding help text lines to maintain consistent formatting. |
+
+No unresolved design questions remain. All decisions recorded in Section 4.
+
+---
+
+## 9. Producer Handoff
+
+### T1: Audit Hit List
+
+- **Producer**: code-writer
+- **Output format**: Markdown document
+- **Filename**: `docs/project_notes/trunk/audit/plan-rename-hitlist.md`
+- **Target line count**: 200-300 lines (depends on actual hit count)
+- **Instruction tone**: Methodical, exhaustive. Run every grep pattern. Categorize every hit. Do not skip files. Do not guess categories -- apply the disambiguation rules literally.
+
+**Content blocks in order**:
+1. Header with generation metadata (date, patterns used, scope)
+2. Summary counts (total hits, RENAME count, KEEP count)
+3. Per-file tables (alphabetical by path), each with Line/Content/Category/Notes columns
+4. Borderline cases section with explicit rationale for each
+
+### T6: Script and Package Config Updates
+
+- **Producer**: code-writer
+- **Output format**: Direct file edits (JavaScript, JSON)
+- **Filenames in edit order**:
+  1. `scripts/install-skills.js` (3 edits)
+  2. `scripts/uninstall-skills.js` (2 edits)
+  3. `package.json` (1 edit)
+- **Target line count**: Net +6 lines in install-skills.js (legacy block insertion), +2 lines in uninstall-skills.js (legacy entry), 0 net in package.json
+- **Instruction tone**: Precise, mechanical. Match existing code patterns exactly. Use content matching for edit anchors (not line numbers, per V1). Preserve existing indentation, spacing, and comment style.
+
+**Content blocks per file**:
+
+`scripts/install-skills.js`:
+1. Edit skill list array: `'intuition-plan'` -> `'intuition-outline'`
+2. Insert legacy cleanup block after `intuition-execute` block (match pattern of lines 105-110)
+3. Edit help text line: update skill name and description, maintain column alignment
+
+`scripts/uninstall-skills.js`:
+1. Edit active skill list: `'intuition-plan'` -> `'intuition-outline'`
+2. Insert legacy entry with version comment before closing `];`
+
+`package.json`:
+1. Edit description: `plan` -> `outline` in phase enumeration
+
+### T8: Verification Sweep
+
+- **Producer**: code-writer
+- **Output format**: Executable verification script + markdown report
+- **Filenames in creation order**:
+  1. Verification commands (executed inline, not a separate script file)
+  2. `docs/project_notes/trunk/verification/devops-infrastructure-verification.md` (report)
+- **Target line count**: Report 80-120 lines
+- **Instruction tone**: Systematic, binary. Every check produces PASS or FAIL. No subjective assessments. If a check fails, document exactly what was found and what was expected.
+
+**Content blocks in order**:
+1. Run Phase 1 grep patterns, record results
+2. Run Phase 2 structural checks, record results
+3. Run Phase 3 migration handler test (if handler file is locatable), record results
+4. Run Phase 4 cross-reference checks, record results
+5. Write verification report with all results in specified format