@tgoodington/intuition 10.6.0 → 10.8.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tgoodington/intuition",
-  "version": "10.6.0",
+  "version": "10.8.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",

package/skills/intuition-prompt/SKILL.md

@@ -130,11 +130,32 @@ If the user's initial CAPTURE response already covers some dimensions, skip them
 
 Every question in REFINE follows these principles:
 
-**Derive from their words.** Your options come from what the user said, not from external research or generic categories. The number of options reflects the actual decision space. Examples at different scales:
+**Derive from their words.** Your options come from what the user said, not from external research or generic categories.
 
-- Binary: "You said 'handle transfers' — does that mean (a) bulk migration when someone leaves, or (b) real-time co-ownership?"
-- Ternary: "You mentioned 'fast' — is that (a) sub-second response times, (b) same-day turnaround, or (c) perceived speed through progressive loading?"
-- Wider: "The notification system could be (a) email-only, (b) in-app real-time, (c) digest-based batching, or (d) user-configured per event type."
+**MANDATORY OPTION ENUMERATION — execute this before EVERY AskUserQuestion call:**
+
+```
+STEP 1: In your thinking, brainstorm EVERY distinct possibility the user's
+        words and context imply. Write them all out. Do not stop at 3.
+STEP 2: Count them. If you have exactly 3, you are almost certainly anchored.
+        Go back to Step 1 and ask: "What am I collapsing together that is
+        actually two distinct things? What possibility am I forgetting?"
+STEP 3: Only proceed when your count genuinely reflects the decision space.
+        2 is fine. 4 is fine. 7 is fine. 3 is fine ONLY if you passed Step 2
+        and confirmed the space truly has exactly 3 distinct options.
+STEP 4: Use ALL the possibilities from your enumeration as AskUserQuestion
+        options. Do not trim to fit a round number.
+```
+
+If you skip this procedure or present 3 options without passing Step 2, the protocol has failed.
+
+Examples at different scales:
+
+- 2 options: "You said 'handle transfers' — does that mean (a) bulk migration when someone leaves, or (b) real-time co-ownership?"
+- 3 options (verified): "You mentioned 'fast' — is that (a) sub-second response times, (b) same-day turnaround, or (c) perceived speed through progressive loading?"
+- 4 options: "The notification system could be (a) email-only, (b) in-app real-time, (c) digest-based batching, or (d) user-configured per event type."
+- 5 options: "For auth you've got (a) email/password, (b) SSO via existing provider, (c) magic links, (d) OAuth social login, or (e) passkeys."
+- 6+ options: "The dashboard layout could be (a) single KPI grid, (b) tabbed by department, (c) role-based views, (d) customizable drag-and-drop, (e) narrative/report style, or (f) a combined feed with filters."
 
 Always include a trailing "or something else entirely?" when the space might be wider than your options suggest — but do NOT count it as an option or letter it.
 
@@ -360,6 +381,7 @@ These are banned. If you catch yourself doing any of these, stop and correct cou
 - Asking questions you could have asked in turn one (generic background)
 - Staying on the same sub-topic for more than 2 follow-ups when the user is uncertain — flag it as an open question and move on
 - Producing a brief with sections the outline phase doesn't consume
+- **Presenting exactly 3 options without running the Mandatory Option Enumeration procedure** — this is the single most persistent failure mode. If you have 3 options, you MUST have verified via Step 2 that you aren't collapsing or omitting possibilities
 
 ## RESUME LOGIC