oh-my-claude-sisyphus 3.3.4 → 3.3.5

package/agents/planner.md

@@ -114,6 +114,41 @@ If the orchestrator did NOT provide pre-gathered context:
 | "How many files will this touch?" | "Should we prioritize backward compatibility?" |
 | "What's the test coverage?" | "What's your risk tolerance for this change?" |
 
+### MANDATORY: Use AskUserQuestion Tool
+
+When asking user-preference questions (Preference, Requirement, Scope, Constraint, Ownership, Risk tolerance), you MUST use the `AskUserQuestion` tool instead of asking via plain text.
+
+**Why:** This provides a clickable option UI that is faster for users than typing responses.
+
+**How to use:**
+- Question: Clear, specific question ending with "?"
+- Options: 2-4 distinct choices with brief descriptions
+- For open-ended questions where options aren't possible, plain text is acceptable
+- Users can always select "Other" to provide custom input
+
+**Example:**
+Use AskUserQuestion tool with:
+- Question: "What's your priority for this feature?"
+- Options:
+  1. **Speed** - Get it working quickly, polish later
+  2. **Quality** - Take time to do it right
+  3. **Balance** - Reasonable quality in reasonable time
+
+**Question Types That REQUIRE AskUserQuestion:**
+
+| Type | Example Question | Example Options |
+|------|------------------|-----------------|
+| Preference | "What's your priority?" | Speed / Quality / Balance |
+| Requirement | "What's the deadline?" | This week / This month / No deadline |
+| Scope | "Include feature Y?" | Yes / No / Maybe later |
+| Constraint | "Performance requirements?" | Critical / Nice-to-have / Not important |
+| Risk tolerance | "Refactoring acceptable?" | Minimal / Moderate / Extensive |
+
+**When Plain Text is OK:**
+- Questions that need specific values (e.g., "What port number?")
+- Follow-up clarifications on a previous answer
+- Questions with too many possible answers to enumerate
+
 ---
 
 # PHASE 2: PLAN GENERATION TRIGGER

package/docs/CLAUDE.md

@@ -311,6 +311,13 @@ A request is BROAD and needs planning if ANY of:
 3. THEN invoke `planner` skill with gathered context
 4. Planner asks ONLY user-preference questions
 
+### AskUserQuestion in Planning
+
+When in planning/interview mode, use the `AskUserQuestion` tool for preference questions instead of plain text. This provides a clickable UI for faster user responses.
+
+**Applies to**: Planner agent, plan skill, planning interviews
+**Question types**: Preference, Requirement, Scope, Constraint, Risk tolerance
+
 ### Mandatory Architect Verification
 
 **HARD RULE: Never claim completion without Architect approval.**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "oh-my-claude-sisyphus",
-  "version": "3.3.4",
+  "version": "3.3.5",
   "description": "Multi-agent orchestration system for Claude Code - Inspired by oh-my-opencode",
   "type": "module",
   "main": "dist/index.js",

package/skills/plan/SKILL.md

@@ -18,6 +18,7 @@ I will ask clarifying questions to fully understand your requirements before cre
 
 ### What Happens Next
 1. **Interview** - I'll ask questions about your goals, constraints, and preferences
+   - Questions will use the AskUserQuestion tool for easy option selection (clickable UI instead of typing)
 2. **Analysis** - Analyst will analyze for hidden requirements and risks
 3. **Planning** - I'll create a comprehensive work plan
 4. **Review** (optional) - Critic can review the plan for quality

package/skills/planner/SKILL.md

@@ -22,6 +22,17 @@ Ask clarifying questions about: Goals, Constraints, Context, Risks, Preferences
 
 **CRITICAL**: Don't assume. Ask until requirements are clear.
 
+**IMPORTANT**: Use the `AskUserQuestion` tool when asking preference questions. This provides a clickable UI for faster responses.
+
+**Question types requiring AskUserQuestion:**
+- Preference (speed vs quality)
+- Requirement (deadline)
+- Scope (include feature Y?)
+- Constraint (performance needs)
+- Risk tolerance (refactoring acceptable?)
+
+**When plain text is OK:** Questions needing specific values (port numbers, names) or follow-up clarifications.
+
 ### Phase 2: Analysis
 Consult Analyst for hidden requirements, edge cases, risks.