@tgoodington/intuition 9.4.0 → 9.5.0

package/skills/intuition-design/SKILL.md

@@ -125,10 +125,10 @@ From the design brief, extract:
 
 Create the directory `{context_path}/.design_research/[item_name]/` if it does not exist.
 
-**Agent 1 — Existing Work Scan** (subagent_type: Explore, model: haiku):
+**Agent 1 — Existing Work Scan** (subagent_type: `intuition-researcher`):
 Prompt: "Search the project for existing work related to [item description]. Look for: prior documentation, existing implementations, reference material, patterns that inform this design. Check docs/, src/, and any relevant directories. Report findings in under 400 words. Facts only."
 
-**Agent 2 — Context Mapping** (subagent_type: Explore, model: haiku):
+**Agent 2 — Context Mapping** (subagent_type: `intuition-researcher`):
 Prompt: "Map the context surrounding [item description]. What already exists that this design must work with or within? What are the boundaries and integration points? Check the codebase structure, existing docs, and configuration. Report in under 400 words. Facts only."
 
 When both return, combine results and write to `{context_path}/.design_research/[item_name]/context.md`.
@@ -156,7 +156,7 @@ Domain-adaptive focus questions:
 
 Each turn: 2-4 sentences of analysis referencing research findings, then ONE question via AskUserQuestion with 2-4 options.
 
-**Research triggers:** If an element definition requires investigating existing patterns or prior art, launch a targeted haiku agent. WAIT for results before continuing the dialogue.
+**Research triggers:** If an element definition requires investigating existing patterns or prior art, launch a targeted `intuition-researcher` agent. WAIT for results before continuing the dialogue.
 
 # PHASE 3: CONNECTIONS (1-2 turns) [ECD: C]
 
@@ -184,7 +184,7 @@ Domain-adaptive focus questions:
 
 This phase gets the most turns because dynamics design often reveals new elements or connection needs. If a gap appears, loop back briefly to address it.
 
-**Research triggers:** For complex design questions requiring deeper analysis, launch a sonnet agent (subagent_type: general-purpose, model: sonnet) for trade-off analysis. Limit: 1 at a time, 600-word responses. WAIT for results before continuing the dialogue.
+**Research triggers:** For complex design questions requiring deeper analysis, launch an `intuition-researcher` agent (model override: sonnet) for trade-off analysis. Limit: 1 at a time, 600-word responses. WAIT for results before continuing the dialogue.
 
 # PHASE 5: FORMALIZATION (1 turn)
 
@@ -354,12 +354,12 @@ Working files in `.design_research/` enable resuming interrupted design sessions
 
 ## Context Research (launched in Phase 1)
 
-Launch 2 haiku Explore agents in parallel via Task tool. See Phase 1, Step 2 for prompt templates. Write combined results to `.design_research/[item_name]/context.md`.
+Launch 2 `intuition-researcher` agents in parallel via Task tool. See Phase 1, Step 2 for prompt templates. Write combined results to `.design_research/[item_name]/context.md`.
 
 ## Targeted Research (launched on demand in Phases 2-4)
 
-- Use haiku Explore agents for fact-gathering (e.g., "What patterns exist in the project for this kind of thing?")
-- Use sonnet general-purpose agents for trade-off analysis (e.g., "Compare approach X and Y given the existing context")
+- Use `intuition-researcher` agents for fact-gathering (e.g., "What patterns exist in the project for this kind of thing?")
+- Use `intuition-researcher` agents (model override: sonnet) for trade-off analysis (e.g., "Compare approach X and Y given the existing context")
 - Each prompt MUST specify the design question and a 400-word limit (600 for sonnet)
 - Write results to `.design_research/[item_name]/options_[topic].md`
 - NEVER launch more than 2 agents simultaneously

package/skills/intuition-detail/SKILL.md

@@ -93,7 +93,7 @@ Ensure the `{context_path}/scratch/` directory exists (create via Bash `mkdir -p
 
 ### Light Tasks (single-pass bypass)
 
-Spawn an opus Task subagent that combines exploration AND specification in one pass:
+Spawn an `intuition-synthesizer` agent that combines exploration AND specification in one pass:
 - **System prompt**: Stage 1 Protocol text + Stage 2 Protocol text (concatenated with a separator)
 - **Task context**: plan tasks, research patterns from profile frontmatter, prior blueprints, outline Section 10 context
 - **Output instruction**: "Research the project, then produce the complete blueprint directly. No user gate — use your best judgment for all decisions. Write to `{context_path}/blueprints/{specialist-name}.md`."
@@ -104,7 +104,7 @@ Ensure the `{context_path}/blueprints/` directory exists. After the subagent ret
 
 #### Stage 1a: Research Planning
 
-Spawn a sonnet Task subagent. The system prompt combines a research-planning framing (owned by this skill) with the specialist's domain expertise (from the profile):
+Spawn an `intuition-synthesizer` agent (model override: sonnet). The system prompt combines a research-planning framing (owned by this skill) with the specialist's domain expertise (from the profile):
 
 - **System prompt**: Construct by concatenating:
   1. **Framing (detail skill provides this):**
@@ -148,7 +148,7 @@ After 1a returns, write the specialist's research plan output to `{context_path}
 
 Parse the specialist's research plan output. Enforce the depth-based research cap: Deep tasks allow 3 entries max, Standard tasks allow 2. If the specialist's plan contains more entries than the cap, take ONLY the first {cap} entries and log a warning to the user: "Research plan had {N} items, capped at {cap} per depth policy."
 
-For each `### R{N}:` entry (up to the cap), spawn a haiku Task subagent (subagent_type: `Explore`):
+For each `### R{N}:` entry (up to the cap), spawn an `intuition-researcher` agent:
 - **Task**: the natural language description from the research plan entry
 - **Instruction suffix**: "Search the project codebase thoroughly. Report: file paths found, key patterns observed, relevant code snippets, and any constraints or conventions discovered. Be specific — include exact paths, field names, and data types."
 
@@ -159,7 +159,7 @@ If any research agent finds nothing relevant, note this — the specialist needs
 #### Stage 1c: Analysis and Synthesis (Resume 1a or Fresh)
 
 **Normal flow:** Resume the Stage 1a specialist subagent using the saved agent ID.
-**Crash recovery flow (no agent ID):** Spawn a fresh opus Task subagent. Provide the specialist's Stage 1 Exploration Protocol as system prompt, and include the saved research plan from `{context_path}/scratch/{specialist-name}-research-plan.md` as additional context so the fresh agent understands what was asked for.
+**Crash recovery flow (no agent ID):** Spawn a fresh `intuition-synthesizer` agent. Provide the specialist's Stage 1 Exploration Protocol as system prompt, and include the saved research plan from `{context_path}/scratch/{specialist-name}-research-plan.md` as additional context so the fresh agent understands what was asked for.
 
 In either case, provide this prompt (the synthesis framing is owned by this skill, not the specialist):
 
@@ -335,7 +335,7 @@ Mark these decisions with `"classified_by": "detail"` in decisions.json.
 
 ## STEP 7: STAGE 2 — SPECIFICATION SUBAGENT
 
-Spawn a FRESH opus Task subagent (do NOT resume Stage 1):
+Spawn a FRESH `intuition-synthesizer` agent (do NOT resume Stage 1):
 - **System prompt**: the specialist's Stage 2 Specification Protocol text (extracted in Step 3)
 - **Injected context**:
   - Full contents of `{context_path}/scratch/{specialist-name}-stage1.md`
@@ -402,11 +402,11 @@ If the COMPLETED specialist was Deep depth, recommend: "Context is heavy — con
 
 Triggers when Step 8d finds no remaining specialists.
 
-**9a. Conflict detection.** Spawn a haiku Task subagent: "Read all blueprint files in `{context_path}/blueprints/`. Compare for: contradictory decisions, overlapping file modifications with conflicting changes, inconsistent interface assumptions, and duplicated work. Write findings to `{context_path}/blueprint-conflicts.md`. If no conflicts, write 'No conflicts detected.'" Wait for completion. If conflicts found, present to user via AskUserQuestion and resolve before continuing.
+**9a. Conflict detection.** Spawn an `intuition-researcher` agent: "Read all blueprint files in `{context_path}/blueprints/`. Compare for: contradictory decisions, overlapping file modifications with conflicting changes, inconsistent interface assumptions, and duplicated work. Write findings to `{context_path}/blueprint-conflicts.md`. If no conflicts, write 'No conflicts detected.'" Wait for completion. If conflicts found, present to user via AskUserQuestion and resolve before continuing.
 
 **9b. Vision review.** Skip this step if only 1 specialist completed (no cross-specialist seams to check).
 
-For multi-specialist projects, spawn a sonnet Task subagent:
+For multi-specialist projects, spawn an `intuition-reviewer` agent:
 
 "Read these files:
 1. `{context_path}/prompt_brief.md` — extract Commander's Intent (desired end state, non-negotiables, boundaries) and Success Criteria

package/skills/intuition-engineer/SKILL.md

@@ -101,7 +101,7 @@ Options:
 
 ## STEP 2: FAN-OUT RESEARCH
 
-For each task (or group of related tasks), launch a haiku research subagent via the Task tool (subagent_type: Explore, model: haiku).
+For each task (or group of related tasks), launch an `intuition-researcher` agent via the Task tool.
 
 When constructing each prompt, replace bracketed placeholders with actual values from the outline. If the task has known file paths, use the "Known Files" variant. If files are marked TBD, use the "TBD Files" variant.
 

package/skills/intuition-outline/SKILL.md

@@ -99,9 +99,9 @@ Create the directory `{context_path}/.outline_research/` if it does not exist.
 
 **Resume check:** If `{context_path}/.outline_research/orientation.md` already exists AND `{context_path}/.outline_research/decisions_log.md` exists with at least one entry, skip the research agents — read the existing orientation.md and proceed to Step 3. This avoids re-spending tokens on research that hasn't changed.
 
-Launch 2 sonnet research agents in parallel using the Task tool:
+Launch 2 `intuition-researcher` agents in parallel using the Task tool (both calls in a single response):
 
-**Agent 1 — Codebase Topology** (subagent_type: Explore, model: sonnet):
+**Agent 1 — Codebase Topology** (subagent_type: `intuition-researcher`):
 Prompt:
 "The project root is the current working directory. Analyze the codebase structure by following these steps in order:
 
@@ -124,7 +124,7 @@ Report on:
 
 Under 500 words. Facts only, no speculation."
 
-**Agent 2 — Pattern Extraction** (subagent_type: Explore, model: sonnet):
+**Agent 2 — Pattern Extraction** (subagent_type: `intuition-researcher`):
 Prompt:
 "The project root is the current working directory. Analyze codebase patterns by following these steps:
 
@@ -156,7 +156,7 @@ When `active_context` is NOT trunk:
 3. Read parent's outline.md and any design specs at `{parent_path}/design_spec_*.md`.
 4. Launch a THIRD orientation research agent alongside the existing two:
 
-**Agent 3 — Parent Intersection Analysis** (subagent_type: Explore, model: sonnet):
+**Agent 3 — Parent Intersection Analysis** (subagent_type: `intuition-researcher`):
 Prompt:
 "The project root is the current working directory. Compare two workflow artifacts:
 
@@ -257,8 +257,8 @@ For each major decision domain identified from the prompt brief, orientation res
 
 1. **Identify** the decision needed. State it clearly.
 2. **Research** (when needed): Launch 1-2 targeted research agents via Task tool.
-   - Use haiku (subagent_type: Explore) for straightforward fact-gathering.
-   - Use sonnet (subagent_type: general-purpose) for trade-off analysis against the existing codebase.
+   - Use `intuition-researcher` for straightforward fact-gathering.
+   - Use `intuition-researcher` (model override: sonnet) for trade-off analysis against the existing codebase.
    - Each agent prompt MUST reference the specific decision domain, return under 400 words.
    - Write results to `{context_path}/.outline_research/decision_[domain].md` (snake_case).
    - NEVER launch more than 2 agents simultaneously.
@@ -606,14 +606,14 @@ If any check fails, fix it before presenting.
 
 ## Tier 1: Orientation (launched in Phase 1)
 
-Launch 2 sonnet Explore agents in parallel via Task tool. See Phase 1, Step 2 for prompt templates. Write combined results to `{context_path}/.outline_research/orientation.md`.
+Launch 2 `intuition-researcher` agents in parallel via Task tool. See Phase 1, Step 2 for prompt templates. Write combined results to `{context_path}/.outline_research/orientation.md`.
 
 ## Tier 2: Decision Research (launched on demand in Phase 3)
 
 Launch 1-2 agents per decision domain when dialogue reveals unknowns needing investigation.
 
-- Use haiku Explore agents for fact-gathering (e.g., "What testing framework does this project use?").
-- Use sonnet general-purpose agents for trade-off analysis (e.g., "Compare approaches X and Y given the current architecture").
+- Use `intuition-researcher` agents for fact-gathering (e.g., "What testing framework does this project use?").
+- Use `intuition-researcher` agents (model override: sonnet) for trade-off analysis (e.g., "Compare approaches X and Y given the current architecture").
 - Each prompt MUST specify the decision domain and a 400-word limit.
 - Reference specific files or directories when possible.
 - Write results to `{context_path}/.outline_research/decision_[domain].md`.

package/skills/intuition-prompt/SKILL.md

@@ -327,12 +327,11 @@ You do NOT launch research subagents by default. Research fires ONLY in this sce
 - "Are there compliance requirements for Z?"
 - "What do other teams typically use for this?"
 
-**Action:** Launch ONE targeted Task call:
+**Action:** Launch ONE targeted `intuition-researcher` agent:
 
 ```
 Description: "Research [specific question]"
-Subagent type: Explore
-Model: haiku
+Subagent type: intuition-researcher
 Prompt: "Research [specific question from the user].
 Context: [what the user is building].
 Search the web and local codebase for relevant information.

package/skills/intuition-test/SKILL.md

@@ -40,7 +40,7 @@ On startup, before reading any files:
 
 ```
 Step 1: Read context (state, build_report, blueprints, decisions, outline)
-Step 2: Analyze test infrastructure (2 parallel haiku Explore agents)
+Step 2: Analyze test infrastructure (2 parallel intuition-researcher agents)
 Step 3: Design test strategy (self-contained domain reasoning)
 Step 4: Confirm test plan with user
 Step 5: Create tests (delegate to sonnet code-writer subagents)
@@ -86,9 +86,9 @@ From decisions files, build a decision index:
 - Map each `[SPEC]` decision to its chosen option and rationale
 - This index is used in Step 6 for fix boundary checking
 
-## STEP 2: RESEARCH (2 Parallel Haiku Explore Agents)
+## STEP 2: RESEARCH (2 Parallel Research Agents)
 
-Spawn two haiku Explore agents in parallel (both Task calls in a single response). Do NOT use `run_in_background` — you MUST wait for both agents to return before proceeding to Step 3:
+Spawn two `intuition-researcher` agents in parallel (both Task calls in a single response). Do NOT use `run_in_background` — you MUST wait for both agents to return before proceeding to Step 3:
 
 **Agent 1 — Test Infrastructure:**
 "Search the project for test infrastructure. Find: test framework and runner (jest, vitest, mocha, pytest, etc.), test configuration files, existing test directories and naming conventions, mock/fixture patterns, test utility helpers, CI test commands, coverage configuration and thresholds. Report exact paths and configuration values."
@@ -203,9 +203,9 @@ Options:
 
 ## STEP 5: CREATE TESTS
 
-Delegate test creation to sonnet Task subagents. Parallelize independent test files (multiple Task calls in a single response). Do NOT use `run_in_background` — you MUST wait for ALL subagents to return before proceeding to Step 6.
+Delegate test creation to `intuition-code-writer` agents. Parallelize independent test files (multiple Task calls in a single response). Do NOT use `run_in_background` — you MUST wait for ALL subagents to return before proceeding to Step 6.
 
-For each test file, spawn a sonnet subagent:
+For each test file, spawn an `intuition-code-writer` agent:
 
 ```
 You are a test writer. Create a test file following these specifications exactly.
@@ -244,9 +244,9 @@ For each failure, classify:
 
 | Classification | Action |
 |---|---|
-| **Test bug** (wrong assertion, incorrect mock, import error) | Fix autonomously — haiku Task subagent |
-| **Implementation bug, trivial** (off-by-one, missing null check, typo — 1-3 lines) | Fix directly — haiku Task subagent |
-| **Implementation bug, moderate** (logic error, missing handler — contained to one file) | Fix — sonnet Task subagent with full diagnosis |
+| **Test bug** (wrong assertion, incorrect mock, import error) | Fix autonomously — `intuition-code-writer` agent |
+| **Implementation bug, trivial** (off-by-one, missing null check, typo — 1-3 lines) | Fix directly — `intuition-code-writer` agent |
+| **Implementation bug, moderate** (logic error, missing handler — contained to one file) | Fix — `intuition-code-writer` agent with full diagnosis |
 | **Implementation bug, complex** (multi-file structural issue) | Escalate to user |
 | **Fix would violate [USER] decision** | STOP — escalate to user immediately |
 | **Fix would violate [SPEC] decision** | Note the conflict, proceed with fix (specialist had authority) |