What problem does it solve? Teams often jump from a raw idea straight into code or specs without questioning the problem, weighing alternatives, or checking whether the work is already tracked. This Skill structures that pre-artifact conversation so ideas are challenged, "build nothing" is seriously considered, and the conclusion routes to the right next step. ## Core Features & Use Cases - Structured divergent exploration: Asks open questions one at a time, checks answers against the repository first, and always puts at least two alternatives plus a do-nothing option on the table. - Read-only tracker reality check: Searches existing issues and PRs (when a tracker descriptor is installed) to surface work that is already tracked or in progress before recommending new artifacts. - Challenger gate and routing: Dispatches a skeptical subagent to attack the tentative conclusion, then routes to exactly one exit ramp — answer only, park as issue, write a spec, or make a small change — and emits machine-parseable Next:/Brief: lines for orchestrators. - Use Case: A user says "I have an idea for a plugin system — should we build it?" The Skill explores the problem, finds a related open issue, challenges the conclusion, and after user confirmation writes a brief and routes to om-prepare-issue. ## Quick Start Ask the assistant to brainstorm whether we should build a plugin system for the CLI before writing any spec or code.
