@tgoodington/intuition 9.4.0 → 9.5.0

package/.claude-plugin/marketplace.json

@@ -0,0 +1,25 @@
+{
+  "name": "intuition",
+  "owner": {
+    "name": "Intuition Contributors",
+    "email": "tgoodington@users.noreply.github.com"
+  },
+  "metadata": {
+    "description": "Domain-adaptive workflow system for Claude Code with specialist teams and format producers.",
+    "version": "9.4.0"
+  },
+  "plugins": [
+    {
+      "name": "intuition",
+      "source": ".",
+      "description": "Domain-adaptive workflow system: prompt, outline, assemble, detail, build, test. 15 skills, 14 domain specialists, 6 format producers.",
+      "version": "9.4.0",
+      "author": {
+        "name": "Intuition Contributors"
+      },
+      "license": "MIT",
+      "keywords": ["workflow", "planning", "execution", "specialists", "producers", "orchestration"],
+      "category": "productivity"
+    }
+  ]
+}

package/.claude-plugin/plugin.json

@@ -0,0 +1,11 @@
+{
+  "name": "intuition",
+  "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 and v9 specialist workflows with 14 domain specialists and 6 format producers.",
+  "version": "9.4.0",
+  "author": {
+    "name": "Intuition Contributors"
+  },
+  "repository": "https://github.com/tgoodington/intuition",
+  "license": "MIT",
+  "keywords": ["workflow", "planning", "execution", "specialists", "producers", "orchestration"]
+}

package/agents/intuition-code-writer.md

@@ -0,0 +1,22 @@
+---
+name: intuition-code-writer
+description: >
+  Trusted code implementer for Intuition workflows. Use when a skill needs files
+  written or modified — producing deliverables from blueprints, creating test files,
+  implementing fixes. Follows specifications exactly without adding unrequested features.
+model: sonnet
+tools: Read, Write, Edit, Glob, Grep, Bash
+permissionMode: acceptEdits
+maxTurns: 50
+---
+
+You are a senior developer implementing code changes. When given a task:
+
+1. Read the specification or blueprint you are pointed to — from disk, not from the prompt.
+2. Read existing code to understand project conventions (naming, style, patterns, imports).
+3. Implement exactly what is specified. Do not add features, refactor surrounding code, or improve things you weren't asked to touch.
+4. Follow the project's existing patterns for error handling, logging, and testing conventions.
+5. If the specification is ambiguous, pick the simplest interpretation that satisfies the requirements.
+6. Report what you created or changed — file paths, function names, key decisions.
+
+Do not add comments explaining obvious code. Do not add type annotations the project doesn't use. Do not introduce new dependencies unless the specification requires them. Match the codebase, not your preferences.

package/agents/intuition-researcher.md

@@ -0,0 +1,21 @@
+---
+name: intuition-researcher
+description: >
+  Fast read-only codebase explorer for Intuition workflows. Use when a skill needs
+  parallel research into project structure, patterns, conventions, test infrastructure,
+  or dependency graphs. Returns concise findings with file paths and evidence.
+model: haiku
+tools: Read, Glob, Grep, Bash
+permissionMode: dontAsk
+maxTurns: 30
+---
+
+You are a fast, focused codebase researcher. When given a research task:
+
+1. Use Glob and Grep to locate relevant files efficiently — target searches, don't scan everything.
+2. Use Read to examine specific files for detail. Read only what you need.
+3. Use Bash only for commands like `wc -l`, `git log`, or tool version checks — never for file reading.
+4. Report findings with exact file paths and line numbers.
+5. Stay under 500 words unless explicitly told otherwise.
+
+Be thorough but fast. Prioritize evidence over speculation. If you can't find something, say so — don't guess. Report what exists, not what you think should exist.

package/agents/intuition-reviewer.md

@@ -0,0 +1,29 @@
+---
+name: intuition-reviewer
+description: >
+  Deliverable reviewer for Intuition workflows. Use when a skill needs quality
+  verification — checking produced files against blueprints, reviewing code for
+  correctness and security, validating test coverage. Reports PASS or FAIL with evidence.
+model: sonnet
+tools: Read, Glob, Grep, Bash
+permissionMode: dontAsk
+maxTurns: 30
+---
+
+You are a rigorous deliverable reviewer. When given a review task:
+
+1. Read the specification or blueprint you are pointed to — from disk.
+2. Read the deliverable(s) being reviewed — from disk.
+3. Check every requirement in the specification against the deliverable. Be systematic.
+4. For code deliverables, also check:
+   - Security: injection risks, exposed secrets, unsafe operations
+   - Correctness: logic errors, off-by-one, null handling, edge cases
+   - Conventions: does it match the project's existing patterns?
+5. Report your verdict: **PASS** (all requirements met) or **FAIL** (list specific issues).
+
+For each issue found, provide:
+- What is wrong (specific, not vague)
+- Where it is (file path and line number or section)
+- Why it matters (what breaks or what requirement it violates)
+
+Do not suggest improvements beyond the specification scope. Do not fail a deliverable for style preferences. Focus on correctness, completeness, and security.

package/agents/intuition-synthesizer.md

@@ -0,0 +1,29 @@
+---
+name: intuition-synthesizer
+description: >
+  Domain analysis and synthesis agent for Intuition workflows. Use when a skill needs
+  deep reasoning to combine research findings into structured analysis, produce blueprints
+  from exploration data, or synthesize cross-cutting insights from multiple sources.
+model: opus
+tools: Read, Write, Edit, Glob, Grep
+permissionMode: default
+maxTurns: 50
+---
+
+You are a domain expert performing deep analysis and synthesis. When given a task:
+
+1. Read all source materials you are pointed to — research findings, prior analysis, blueprints, specifications.
+2. Identify patterns, conflicts, gaps, and insights across the sources.
+3. Produce structured output in the format requested by the calling skill.
+4. Ground every conclusion in evidence from the source materials. Cite specific files and findings.
+5. Flag uncertainties explicitly — distinguish between what you know, what you infer, and what you're unsure about.
+
+When producing blueprints or specifications:
+- Be precise about interfaces, data flows, and dependencies.
+- Call out assumptions that need validation.
+- Identify edge cases and failure modes.
+
+When detecting conflicts or gaps:
+- State exactly what conflicts with what, citing both sources.
+- Assess severity: blocking (must resolve before proceeding) vs advisory (note and continue).
+- Suggest resolution options when the evidence supports them.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tgoodington/intuition",
-  "version": "9.4.0",
+  "version": "9.5.0",
   "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.",
   "keywords": [
     "claude-code",
@@ -23,6 +23,8 @@
     "test": "node bin/intuition.js help"
   },
   "files": [
+    ".claude-plugin/",
+    "agents/",
     "bin/",
     "skills/",
     "specialists/",

package/scripts/install-skills.js

@@ -1,11 +1,11 @@
 #!/usr/bin/env node
 
 /**
- * Installation script for Intuition skills, specialists, and producers
+ * Installation script for Intuition skills, specialists, producers, and agents
  *
  * This script is run after `npm install -g @tgoodington/intuition`
  * It copies skills to ~/.claude/skills/, specialists to ~/.claude/specialists/,
- * and producers to ~/.claude/producers/ for global access.
+ * producers to ~/.claude/producers/, and agents to ~/.claude/agents/ for global access.
  */
 
 const fs = require('fs');
@@ -77,6 +77,14 @@ const producers = [
   'data-file-writer'
 ];
 
+// Reusable agent definitions (v9.4) — scanned dynamically
+const agentsDir = path.join(__dirname, '..', 'agents');
+const agents = fs.existsSync(agentsDir)
+  ? fs.readdirSync(agentsDir).filter(entry =>
+      entry.endsWith('.md')
+    )
+  : [];
+
 // Main installation logic
 try {
   const homeDir = os.homedir();
@@ -130,6 +138,14 @@ try {
     log(`Created ${claudeProducersDir}`);
   }
 
+  // --- Agents directory (v9.4) ---
+  const claudeAgentsDir = path.join(homeDir, '.claude', 'agents');
+
+  if (!fs.existsSync(claudeAgentsDir)) {
+    fs.mkdirSync(claudeAgentsDir, { recursive: true });
+    log(`Created ${claudeAgentsDir}`);
+  }
+
   // Install each skill
   skills.forEach(skillName => {
     const src = path.join(packageRoot, 'skills', skillName);
@@ -175,6 +191,23 @@ try {
     }
   });
 
+  // Install each agent definition (flat .md files)
+  if (agents.length === 0) {
+    log(`No agent definitions found in ${agentsDir} — skipping agent install`);
+  }
+  agents.forEach(agentFile => {
+    const src = path.join(agentsDir, agentFile);
+    const dest = path.join(claudeAgentsDir, agentFile);
+
+    if (fs.existsSync(src)) {
+      fs.copyFileSync(src, dest);
+      log(`\u2713 Installed ${agentFile} agent to ${dest}`);
+    } else {
+      error(`${agentFile} agent not found at ${src}`);
+      process.exit(1);
+    }
+  });
+
   // Verify installation
   const allSkillsInstalled = skills.every(skillName =>
     fs.existsSync(path.join(claudeSkillsDir, skillName))
@@ -185,8 +218,11 @@ try {
   const allProducersInstalled = producers.every(name =>
     fs.existsSync(path.join(claudeProducersDir, name))
   );
+  const allAgentsInstalled = agents.every(name =>
+    fs.existsSync(path.join(claudeAgentsDir, name))
+  );
 
-  if (allSkillsInstalled && allSpecialistsInstalled && allProducersInstalled) {
+  if (allSkillsInstalled && allSpecialistsInstalled && allProducersInstalled && allAgentsInstalled) {
     log(`\u2713 Installation complete!`);
     log(`Skills are now available globally:`);
     log(`  /intuition-start          - Load project context and detect workflow phase`);
@@ -209,6 +245,8 @@ try {
     specialists.forEach(name => log(`  ${name}`));
     log(`Format producers (${producers.length}):`);
     producers.forEach(name => log(`  ${name}`));
+    log(`Reusable agents (${agents.length}):`);
+    agents.forEach(name => log(`  ${name.replace('.md', '')}`));
     log(`\nYou can now use these skills in any project with Claude Code.`);
   } else {
     error(`Verification failed - not all components properly installed`);

package/scripts/uninstall-skills.js

@@ -1,10 +1,10 @@
 #!/usr/bin/env node
 
 /**
- * Uninstallation script for Intuition skills
+ * Uninstallation script for Intuition skills, agents, specialists, and producers
  *
  * This script is run before `npm uninstall -g @tgoodington/intuition`
- * It removes all Intuition skills from ~/.claude/skills/
+ * It removes all Intuition components from ~/.claude/
  */
 
 const fs = require('fs');
@@ -72,6 +72,23 @@ try {
     }
   });
 
+  // Remove Intuition agent definitions
+  const claudeAgentsDir = path.join(homeDir, '.claude', 'agents');
+  const agentsToRemove = [
+    'intuition-researcher.md',
+    'intuition-code-writer.md',
+    'intuition-reviewer.md',
+    'intuition-synthesizer.md'
+  ];
+
+  agentsToRemove.forEach(agentFile => {
+    const agentDest = path.join(claudeAgentsDir, agentFile);
+    if (fs.existsSync(agentDest)) {
+      fs.rmSync(agentDest, { force: true });
+      log(`\u2713 Removed ${agentFile} agent from ${agentDest}`);
+    }
+  });
+
   // Clean up empty .claude/skills directory if it's empty
   if (fs.existsSync(claudeSkillsDir)) {
     const remaining = fs.readdirSync(claudeSkillsDir);

package/skills/intuition-assemble/SKILL.md

@@ -46,7 +46,10 @@ Scan three tiers in priority order. Deduplicate by `name` — first found wins.
 
 1. Glob `.claude/specialists/*/*.specialist.md` (project-level)
 2. Glob `~/.claude/specialists/*/*.specialist.md` (user-level, expand `~` via Bash)
-3. Determine the Intuition package root: run `node -e "console.log(require.resolve('@tgoodington/intuition/package.json'))"` via Bash, extract the directory. Glob `{package_root}/specialists/*/*.specialist.md`.
+3. Framework-bundled specialists — try in order, stop at first success:
+   a. **Plugin path**: Glob `${CLAUDE_PLUGIN_ROOT}/specialists/*/*.specialist.md`. If `${CLAUDE_PLUGIN_ROOT}` is empty or the glob returns nothing, fall through.
+   b. **npm path**: Run `node -e "console.log(require.resolve('@tgoodington/intuition/package.json'))"` via Bash, extract the directory. Glob `{package_root}/specialists/*/*.specialist.md`.
+   c. **Fallback**: Glob `node_modules/@tgoodington/intuition/specialists/*/*.specialist.md` relative to project root.
 
 For each profile found: read ONLY the YAML frontmatter using `Read` with `limit: 30` (frontmatter is typically under 25 lines). Extract `name` and `domain_tags`. Do NOT read the full profile body — the Stage 1/2 protocols are not needed for matching. Build a specialists list.
 
@@ -54,13 +57,14 @@ If zero specialists found after all three tiers, HALT with this message:
 "No specialist profiles found. Install specialist profiles in one of these locations:
 - `.claude/specialists/` (project-level)
 - `~/.claude/specialists/` (user-level)
-- Or ensure `@tgoodington/intuition` is installed with its bundled specialists."
+- Install the Intuition plugin: `/plugin install intuition`
+- Or install via npm: `npm install -g @tgoodington/intuition`"
 
 ### Step 3: Scan Producer Registry
 
-Same three-tier pattern using `producers/` directories and `*.producer.md` files. Read ONLY the YAML frontmatter using `Read` with `limit: 30`. Extract `name` and `output_formats` from each. Do NOT read the full profile body. Deduplicate by name with same priority (first found wins).
+Same three-tier pattern as Step 2, using `producers/` directories and `*.producer.md` files. Tier 3 uses the same resolution order (plugin path → npm path → fallback). Read ONLY the YAML frontmatter using `Read` with `limit: 30`. Extract `name` and `output_formats` from each. Do NOT read the full profile body. Deduplicate by name with same priority (first found wins).
 
-If zero producers found, HALT with the same pattern message referencing producer directories.
+If zero producers found, HALT with the same pattern message referencing producer directories and install methods.
 
 ### Step 4: Team Assembly (Inline Matching)
 
@@ -319,7 +323,7 @@ Set on root: `last_handoff` → current ISO timestamp, `last_handoff_transition`
 
 - **Zero specialists found**: Halt at Step 2 with install instructions.
 - **Zero producers found**: Halt at Step 3 with install instructions.
-- **Package root resolution fails**: Fallback to scanning `node_modules/@tgoodington/intuition/` relative to project root.
+- **Framework-bundled resolution fails**: Tier 3 tries plugin path, then npm resolution, then local node_modules. If all three fail, Tiers 1 and 2 may still have results.
 - **All tasks unmatched**: Present the full unmatched list at Step 6. If user chooses to create specialists, write the request file and route to agent-advisor. Do not silently skip everything.
 - **User rejects team**: Allow adjustments, re-present. Do not write anything until approved.
 - **Prerequisites missing**: Halt with exact install commands. Do not proceed to team confirmation.

package/skills/intuition-build/SKILL.md

@@ -150,7 +150,7 @@ For each task per `team_assignment.json` execution order (parallelize tasks with
    - User: `~/.claude/producers/{producer-name}/{producer-name}.producer.md`
    - Framework-shipped: scan the `producers/` directory at the package root
 4. Construct the delegation prompt using the producer profile as system instructions. Direct the subagent to READ the blueprint from disk (do NOT inject blueprint content into the prompt — this avoids duplicating large files in both parent and subagent contexts). Only include non-test output files in the delegation.
-5. Spawn the producer as a Task subagent using the model declared in the producer profile.
+5. Spawn the producer as an `intuition-code-writer` agent (or appropriate producer-specific agent if one exists). Use the model declared in the producer profile.
 
 **Producer delegation format:**
 ```
@@ -180,7 +180,7 @@ After producers complete deliverables, execute all three review layers. **Batch
 
 1. Identify the specialist that authored the blueprint (from blueprint YAML frontmatter `specialist` field).
 2. Locate that specialist's profile path in the registry (same scan order as producers: project → user → framework).
-3. Spawn a review subagent with adversarial framing. Use the `reviewer_model` declared in the specialist profile's YAML frontmatter. If this specialist produced multiple deliverables, include ALL of them (up to 3) in a single review subagent.
+3. Spawn an `intuition-reviewer` agent with adversarial framing. Use the `reviewer_model` declared in the specialist profile's YAML frontmatter. If this specialist produced multiple deliverables, include ALL of them (up to 3) in a single review agent.
 
 **Specialist review delegation format:**
 ```
@@ -224,9 +224,9 @@ Log all deviations (additions and omissions) in the build report's "Deviations f
 ### Layer 3: Mandatory Cross-Cutting Reviewers
 
 1. Check the specialist profile's `mandatory_reviewers` field in its YAML frontmatter.
-2. For EACH mandatory reviewer listed: locate their specialist profile, spawn a review subagent using their `reviewer_model`.
-3. **Security Expert is ALWAYS mandatory** — even if `mandatory_reviewers` is empty. Spawn a Security Expert review for every deliverable that produces code, configuration, or scripts.
-4. **Batch cross-cutting reviews** the same way as Layer 1: include up to 3 deliverables per review subagent. If all code deliverables in the current execution phase share the same cross-cutting reviewer, batch them into one review call.
+2. For EACH mandatory reviewer listed: locate their specialist profile, spawn an `intuition-reviewer` agent using their `reviewer_model`.
+3. **Security Expert is ALWAYS mandatory** — even if `mandatory_reviewers` is empty. Spawn a Security Expert `intuition-reviewer` agent for every deliverable that produces code, configuration, or scripts.
+4. **Batch cross-cutting reviews** the same way as Layer 1: include up to 3 deliverables per review agent. If all code deliverables in the current execution phase share the same cross-cutting reviewer, batch them into one review call.
 
 **Cross-cutting review delegation format:**
 ```