skills/challenge/SKILL.md
Two-phase challenge to a proposal/design/plan/analysis. Phase 1 grills the user with one-question-at-a-time interviews to surface assumptions and trade-offs. Phase 2 spawns critic-design with the surfaced material as devil's advocate input. Do NOT use for code review findings (use /audit) or outcome assertion (use /assert which has built-in adversarial testing).
npx skillsauth add thkt/claude-config challengeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Two-phase challenge. Phase 1 grills, Phase 2 spawns critic-design.
$ARGUMENTS: what to challenge (proposal file path or description)$ARGUMENTS is empty: stop and ask user to specify target. Silent target inference from conversation has high misfire risk.Ask one question at a time. Each question must include a recommended answer presented as the top option in AskUserQuestion. Walk down each branch of the design tree, resolving dependencies one-by-one.
| Rule | Detail | | ---- | ------ | | Code-resolvable questions | If the answer lives in the code, run yomu/ugrep/explore instead of asking | | Question budget | Cap at 7 across the phase. If hitting cap with branches still open, summarise the unresolved set and let user decide whether to continue | | Stop conditions | All decision branches resolved, user signals "enough", or budget hit |
Aggregate grill findings into critic-design input schema before spawning.
| Field | Source | | ----- | ------ | | source | "user-grill" | | artifact_type | inferred from $ARGUMENTS (spec / plan / design / ADR / doc) | | approach | one-line summary of the proposal core | | decisions | architectural-level decisions crystallised during grill (terminology checks and scope minutiae excluded) | | trade-offs | trade-offs surfaced during grill | | referenced_files | files cited or read during grill |
| Step | Action | | ---- | ------ | | 1 | Compose Phase 2 input from Phase 1 aggregation + original $ARGUMENTS context | | 2 | Spawn critic-design via Task (subagent_type: critic-design, background: false). Mention ARCHITECTURE.md or equivalent if present | | 3 | Wait for completion, capture verdict + weaknesses |
| Section | Content | | ------- | ------- | | Grill summary | Surfaced assumptions, decisions, trade-offs (one-line each) | | Devil verdict | critic-design output verbatim | | Actionable items | Top 3 concrete actions (keep / remove / revise) |
tools
Internal helper for /think Step 11. Renders SOW.md + Spec.md as an integrated Astro view and returns a dev server URL.
development
Extract repository spec while detecting bugs, spec gaps, and consistency drift via dual-purpose documentation. OUTCOME.md-axis question-driven exploration with ephemeral output. Do NOT use for code review (use /audit or /polish), feature implementation (use /code), planning only (use /think), or single-bug fix (use /fix).
development
Discover undocumented design decisions and challenge each candidate via critic-design before promotion. Rank by impact and reversibility, produce ADR promotion candidates. Treat each candidate as a position arguing for ADR status, not a fact to be filed. Pairs with audit-adr-drift, which scans existing ADRs for drift against code.
development
Scan ADR Decision sections against current code and report drift with modification direction and priority. Do NOT use for repos without ADRs (use audit-adr-gaps instead).