challenge-mewith-docslisted

# /challenge-me with-docs > Same one-question-at-a-time interview as `/challenge-me vision`, plus: > a **session glossary** against `CONTEXT.md`, **load-bearing claim-vs-code > verification**, and an optional `CONTEXT.md` **patch** + **ADR candidates** > appended to the final pitch. `/challenge-me` itself never writes to > disk — the in-interview triggers (`!roadmap`, `!ai`) route to > `/roadmap:create` and `/council default`, which run under their own > contracts. ## Welcome If the user invokes `/challenge-me with-docs` with no body, render once: ``` Drop the seed and I'll grill it against your project docs. Per turn: one question, recommended answer. I'll surface glossary clashes vs CONTEXT.md and verify load-bearing claims against the code. At the end you get a pitch — plus an optional CONTEXT.md patch and ADR candidates to copy / apply yourself. End the interview early any time: `!pitch` — emit pitch, hand back `!roadmap` — emit pitch + auto-route to `/roadmap:create` `!ai` / `!council` — poll the AI council for the open question(s), continue (cost auto-accepted) ``` Skip the welcome if the user invokes `/challenge-me with-docs <seed>` directly. ## When to use this instead of `vision` | Condition | Pick | |---|---| | Project has no `CONTEXT.md` and no ADR dir | `vision` | | Seed uses domain terms that may already be defined elsewhere | `with-docs` | | User says "check against our docs" / "make sure it matches CONTEXT.md" | `with-do