| name | a |
| description | Trigger: /a. Never auto-trigger on think, scan, consider, or examine. |
/analyze - Explore → Interrogate → Bridge
Structured Q&A that converges on decisions. Questions evolve based on answers.
Arguments
/analyze — asks "What needs solving?"
/analyze <topic> — skips opening question
/analyze resume — finds last decision tracker in conversation, continues
Flow
1. EXPLORE
- Read relevant codebase files (5-10). For greenfield projects, ask about constraints instead.
- Identify decision points. Form an opinion on each from codebase evidence.
- Output:
"~N decisions to work through (some will be auto-decided)"
2. INTERROGATE
One question at a time via AskUserQuestion.
Auto-decide when codebase evidence makes one option overwhelmingly correct. Present initial auto-decisions as a batch before the first human question:
### Auto-decided (review before we continue)
1. ✅ (auto) [topic]: [answer] — [rationale]
Ask: "Want to revisit any of these, or move on?" If flagged, convert to regular question.
Questions:
- Order options by recommendation strength (best first)
- All option slots are for real answers — user can type "go back" or "park" via Other
After each answer:
- Reassess: does this reveal new decisions (mark
🆕), kill existing ones (mark ➖)?
- Flag conflicts with previous decisions
- Push back on risky choices even if user seems confident
- If decisions exceed 8, suggest splitting the task before continuing