What problem does it solve? Teams often jump from a vague 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 decisions are deliberate and handoffs are machine-readable. ## Core Features & Use Cases - Divergent exploration: Asks open questions one at a time, always putting at least two alternatives plus a "build nothing" option on the table. - Read-only tracker reality-check: Searches existing issues and PRs so already-tracked ideas route to the existing work instead of duplicates. - Challenger gate: Dispatches a fresh-context skeptical reviewer subagent to attack the conclusion before it is finalized. - Machine-parsed routing: Emits exact Next:, Brief:, and Issue: contract lines so an orchestrator can autonomously run the chosen next skill (om-prepare-issue, om-auto-write-spec, om-spec-writing, om-auto-create-pr, or om-auto-fix-issue). - Use Case: A user says "I have an idea for team invitations." The skill explores the problem, finds no existing issue, confirms routing with the user, writes a handoff brief to the specs directory, and emits Next: om-spec-writing for the orchestrator. ## Quick Start Say "let's think this through" or "should we build this" followed by your idea, and answer the questions one at a time until a routing decision is confirmed.
