challenge-melisted

# /challenge-me Top-level orchestrator for the `/challenge-me` family. Walks a decision tree by asking one question at a time until the agent is confident enough to emit a copyable Markdown pitch. > Also reachable as [`/grill-me`](grill-me.md) — thin alias, identical > behaviour, identical sub-commands and triggers. ## Sub-commands | Sub-command | Routes to | Purpose | |---|---|---| | `/challenge-me vision` | `commands/challenge-me/vision.md` | Standard variant — interrogate a fuzzy plan / idea / ticket draft to 95% confidence, emit a vision pitch | | `/challenge-me with-docs` | `commands/challenge-me/with-docs.md` | Doc-aware variant — same flow plus session glossary against `CONTEXT.md`, load-bearing claim-vs-code verification, optional `CONTEXT.md` patch + ADR candidates in the pitch | ## When to pick which - **`vision`** — greenfield idea, fresh ticket draft, or a plan with no existing project glossary / domain docs. Default for "challenge me on this plan". - **`with-docs`** — the project has `CONTEXT.md`, an ADR directory (`docs/adr/`, `docs/decisions/`, `agents/decisions/`), or the user uses domain terms that may already be defined. The variant catches glossary conflicts and load-bearing claim-vs-code drift before pitch. ## Dispatch 1. Parse the user's argument: `/challenge-me <sub-command> [flags] [seed]`. 2. Look up the sub-command in the table above. 3. Load the body of the routed file and follow its `## Steps` section verbatim with the remaining