@event4u/agent-config 1.21.0 → 1.22.0

package/.agent-src/commands/challenge-me/with-docs.md

@@ -0,0 +1,333 @@
+---
+name: challenge-me:with-docs
+cluster: challenge-me
+sub: with-docs
+description: "Doc-aware /challenge-me — 95%-confidence interview with session glossary vs CONTEXT.md, load-bearing claim-vs-code verification, optional CONTEXT.md patch + ADR candidates in the pitch."
+disable-model-invocation: true
+suggestion:
+  eligible: true
+  trigger_description: "challenge me against the docs, grill me with our context, grill me against the docs, grill me against CONTEXT.md, grill me with the project context, frag mich durch und prüf gegen CONTEXT.md, challenge plan with domain docs"
+  trigger_context: "user wants the seed challenged against existing project glossary, CONTEXT.md, or ADRs — not a greenfield interview"
+---
+
+# /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. Nothing is written to disk — the pitch is
+> the only artefact.
+
+## 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.
+
+Stop early any time by typing `!pitch` (or `!Vision pitchen`).
+```
+
+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-docs` |
+| User says "make sure this is consistent with the codebase" | `with-docs` |
+| Greenfield brainstorm, no existing constraints to honour | `vision` |
+
+If neither file exists and the user invoked `with-docs` anyway, fall
+back gracefully to `vision`-style flow and skip the doc inventory; note
+the absence in a single line at the end of Step 0.
+
+## Stop condition, flags, pitch trigger
+
+Inherits **verbatim** from [`vision.md`](vision.md):
+
+- Default stop = the four 95%-conditions (AND, not OR).
+- Load-bearing test = answer changes goal / scope / hard constraint / AC.
+- `--until=95%` (default) · `--until=N` · `--keep-going`.
+- Pitch trigger: `!pitch`, `/pitch`, or whole reply `pitch`.
+- Step 1 question-block shape, Step 4 pitch validation.
+
+The deltas below replace / extend Step 0, Step 1, Step 2, Step 4 and
+Step 5. Steps 3 and 6 are unchanged.
+
+## Steps
+
+### Step 0 — Inspect (read-only doc inventory + codebase)
+
+```
+EXPLORE THE DOCS AND THE CODEBASE BEFORE THE FIRST QUESTION.
+NEVER WRITE TO DISK IN STEP 0. NEVER ASK WHAT view / grep / codebase-retrieval ANSWERS.
+```
+
+1. **Read the seed** (same as `vision`).
+2. **Doc inventory** — read-only:
+   - `view CONTEXT.md` if it exists; init empty **session glossary** in
+     agent state (in-memory only).
+   - `view CONTEXT-MAP.md` if it exists. If the seed touches > 1 listed
+     context, **ask once** (numbered options listing each context) which
+     to focus on; record the choice, do not re-ask.
+   - Autodetect ADR directory by listing `docs/adr/`, `docs/decisions/`,
+     `docs/architecture/decisions/`, `agents/decisions/`. Pick the
+     **most-recently-modified** non-empty dir; if none exist, default to
+     `docs/adr/` for the patch output (do **not** create the dir).
+   - If `agent state` already holds a session glossary from a prior
+     `/challenge-me with-docs` invocation **in this same chat**, load
+     it. Then re-read `CONTEXT.md` — any term in `CONTEXT.md` overrides
+     the session glossary (disk wins over draft). Emit a delta line if
+     non-zero: `Loaded N draft terms; CONTEXT.md already has X — carrying
+     forward the rest as drafts.`
+3. **Codebase lookup** — same as `vision` Step 0.2 (existing routes,
+   model fields, conventions, feature flags).
+4. **List the open dimensions** internally — same as `vision` Step 0.3.
+
+### Step 1 — Glossary-aware questioning
+
+Every question block runs an extra check **before** emit:
+
+- **Glossary conflict** — does the seed (or a prior turn) use a term
+  that conflicts with the existing `CONTEXT.md` glossary, including a
+  case-insensitive match? → first question of the session is the
+  glossary disambiguation:
+
+  > Your `CONTEXT.md` defines **Account** as the billing entity. Your
+  > seed uses "account" for the logged-in person. Which is it?
+  > 1. **Match CONTEXT.md** — rename "account" in the plan to "user".
+  > 2. Override CONTEXT.md — the plan introduces a new meaning; we patch
+  >    the glossary at pitch time.
+  > 3. Skip / not relevant.
+
+- **Fuzzy / overloaded term** — propose a canonical term as option 1.
+
+- **No glossary present** → skip the check; behave like `vision`.
+
+The glossary check is itself **load-bearing only when the term flips an
+AC or scope boundary OR when it conflicts with an existing CONTEXT.md
+entry**. Pure naming preference with no conflict is closed silently
+(same load-bearing test as `vision`, with the conflict-extension).
+
+Otherwise the question-block shape, recommended-option rule, 3–4 option
+cap, and `Why it matters` requirement are identical to
+[`vision.md § Step 1`](vision.md#step-1-ask-one-question-per-turn).
+
+### Step 2 — Apply the answer + session glossary (in-memory)
+
+Adopt-the-answer rules are identical to
+[`vision.md § Step 2`](vision.md#step-2-apply-the-answer).
+
+When a term is resolved, write to **session glossary** (agent state
+only). **Never write to disk in this step.** Every turn's reply ends
+with a compact echo block when the glossary is non-empty:
+
+```
+**Session glossary (draft, not yet written):**
+- **Cancellation** — refund + reversal, excludes disputes (turn 3)
+- **Account** — maps to `User` entity (turn 5)
+```
+
+After the **fifth** session-glossary turn, condense the echo to:
+
+```
+**Session glossary (draft):** N terms · M ADR candidates — see pitch for full list.
+```
+
+If the session glossary is empty, omit the echo block entirely.
+
+### Step 3 — Re-score and continue
+
+Identical to [`vision.md § Step 3`](vision.md#step-3-re-score-and-continue).
+
+### Step 3.5 — ADR candidate check (no write)
+
+After each branch closes, run the three-test on the resolution:
+
+1. **Hard-to-reverse** — would unwinding it require code or schema rollback?
+2. **Surprising-without-context** — would a future contributor read the
+   choice and ask "why this and not the obvious alternative?"
+3. **Result of a real trade-off** — were the rejected options realistic?
+
+If **all three** pass, append the candidate to an in-memory ADR-candidate
+list. Do **not** ask, do **not** write. Surfaces only in Step 5.
+
+### Step 4 — Validate before pitching
+
+Identical to [`vision.md § Step 4`](vision.md#step-4-validate-before-pitching),
+plus:
+
+- Pitch uses the **canonical glossary spelling** for every term in the
+  session glossary.
+- The `CONTEXT.md` patch block is **always** appended when the session
+  glossary is non-empty — agent has no signal whether the user already
+  applied a previous patch in-chat. The patch block carries a header
+  the user reads before applying (see Step 5).
+
+### Step 5 — Emit the pitch with optional doc patches
+
+Emit the same fenced Markdown pitch as `vision`, then append up to two
+optional sections **inside** the same outer four-backtick fence:
+
+`````markdown
+````markdown
+# <one-line vision title>
+
+**Goal:** <verb + object + observable result>
+
+**In scope:**
+- <bullet>
+
+**Out of scope:**
+- <bullet>
+
+**Constraints (hard):**
+- <bullet>
+
+**Acceptance criteria:**
+1. <observable, testable>
+
+**Open assumptions:**
+- assumes: <line>
+
+**Recommended next step:** <one sentence — e.g. "/work \"<pitch goal>\"" >.
+
+---
+
+**CONTEXT.md patch (apply via `patch -p1` or your IDE's Apply Patch — only
+if you haven't already merged these terms):**
+
+```diff
+@@ ... @@
++ ## Cancellation
++ Refund + reversal, excludes disputes.
+```
+
+**ADR candidate(s) — apply only if useful:**
+- `docs/adr/0007-cancellation-semantics.md` — captures the soft-vs-hard
+  delete decision (hard-to-reverse · surprising · real-tradeoff).
+
+**Glossary touched this session:** Cancellation, Account, Refund (3 terms).
+````
+`````
+
+The outer fence uses **five backticks** so the inner four-backtick fence
+(which itself contains a triple-backtick diff) stays literal when the
+user copies the whole block.
+
+Omission rules:
+
+- Session glossary empty → omit the `CONTEXT.md patch`, `Glossary touched`,
+  and the preceding `---` separator entirely.
+- No ADR candidate qualified → omit the `ADR candidate(s)` section.
+- Both empty → pitch is identical to a `vision` pitch.
+
+### Step 6 — Hand back
+
+Identical to [`vision.md § Step 6`](vision.md#step-6-hand-back). Never
+auto-write the patches, never auto-invoke `/work`.
+
+## Code-vs-claim guard (gated)
+
+When the user states "X is implemented as Y" AND the claim is
+**load-bearing** (would change an AC, scope boundary, or hard
+constraint), agent runs `view` / `grep` / `codebase-retrieval` to
+verify. Mismatch → single question block:
+
+> Your seed says X works via Y. The code (`path/to/file.php:123`) shows
+> it via Z. Which is right?
+> 1. **Code is right, my seed was wrong** — recommended.
+> 2. Seed is right, code is stale — separate fix needed.
+> 3. Both — they're both real paths.
+
+Non-load-bearing claims (cosmetic, naming, internal style) — agent
+trusts the user's statement, no lookup. This gate keeps verification
+cost O(load-bearing-decisions), not O(every-statement).
+
+## Output format
+
+1. **Per-turn question block** — one numbered question with a
+   recommended option, until 95% or pitch trigger.
+2. **Session-glossary echo** — appended every turn while the glossary is
+   non-empty (full list in turns 1–5, condensed line from turn 6 on).
+3. **Final pitch** — a single copyable five-backtick fenced block
+   (Step 5 shape) holding the standard pitch + optional `CONTEXT.md`
+   patch + optional ADR candidates.
+
+## Examples
+
+```
+/challenge-me with-docs
+/challenge-me with-docs Add a per-tenant rate limit on the public API
+/challenge-me with-docs --until=5 Migrate cancellations from soft-delete to hard-delete
+/challenge-me with-docs --keep-going Re-architect the notifications pipeline
+```
+
+## Gotchas
+
+- Inherits every gotcha from
+  [`vision.md § Gotchas`](vision.md#gotchas) — confidence inflation,
+  recommendation drift, stacked questions, too many options.
+- **Glossary clutter** — if the agent echoes the full session glossary
+  past turn 5 the reply gets noisy. Condense per Step 2.
+- **Patch redundancy** — agent has no signal whether the user already
+  applied a previous in-chat `CONTEXT.md` patch. Always emit the patch
+  with the "only if you haven't already merged these terms" header so
+  the user can dedupe.
+- **ADR over-eager** — the three-test (hard-to-reverse · surprising ·
+  real-tradeoff) is the gate. A pure naming choice or a default that
+  could flip without rollback is **not** an ADR candidate.
+- **Multi-context confusion** — if `CONTEXT-MAP.md` lists multiple
+  contexts and the seed touches several, ask **once** in Step 0; never
+  re-ask which context to focus on.
+
+## Rules
+
+- Inherits every rule from [`vision.md § Rules`](vision.md#rules) —
+  one question per turn, no auto-execution, no file writes, codebase
+  first, welcome once, mirror the user's language.
+- **No file writes** — even though this variant produces glossary
+  patches and ADR candidates, those go **into the pitch block** for the
+  user to apply. Agent never writes `CONTEXT.md` or any `docs/adr/*`
+  file itself, per `non-destructive-by-default`.
+- **Two-gate verification** — the glossary check fires on AC-flipping
+  terms OR `CONTEXT.md` conflicts; the code-vs-claim check fires only
+  on load-bearing claims. Non-load-bearing trivia → no lookup, no
+  question.
+- **Session glossary persists within a chat** — a second
+  `/challenge-me with-docs` invocation in the same chat inherits draft
+  terms; disk state (`CONTEXT.md`) overrides drafts on every Step 0.
+
+## Do NOT
+
+- Inherits every prohibition from
+  [`vision.md § Do NOT`](vision.md#do-not).
+- Do NOT write to `CONTEXT.md` directly — emit the diff in the pitch.
+- Do NOT create files in `docs/adr/` — emit the path + rationale in the
+  pitch and let the user create the file.
+- Do NOT verify every user statement — only load-bearing claims trigger
+  the code-vs-claim guard.
+- Do NOT echo the full session glossary past turn 5 — condense.
+
+## See also
+
+- [`/challenge-me vision`](vision.md) — sibling without doc inventory,
+  glossary check, or claim verification.
+- [`/refine-prompt`](../refine-prompt.md) — one-shot prompt scoring.
+- [`/refine-ticket`](../refine-ticket.md) — ticket reconstruction.
+- [`ask-when-uncertain`](../../rules/ask-when-uncertain.md) — the
+  one-question-per-turn Iron Law.
+- [`non-destructive-by-default`](../../rules/non-destructive-by-default.md)
+  — why the patches live in the pitch block, not on disk.
+- Inspiration: `mattpocock/skills/skills/engineering/grill-with-docs/SKILL.md`
+  — same intent (interview against domain docs), restructured to honour
+  the project's non-destructive floor (session glossary in-memory,
+  patches emitted as copyable diffs in the pitch).

package/.agent-src/commands/challenge-me.md

@@ -0,0 +1,61 @@
+---
+name: challenge-me
+description: Challenge-me orchestrator — routes to vision, with-docs
+cluster: challenge-me
+disable-model-invocation: true
+suggestion:
+  eligible: true
+  trigger_description: "challenge me on this plan, grill me, grill me on this, grill me on this plan, grill me through this, grill me until it's clear, grill me hard, frag mich durch, dreh mich durch die Mangel, challenge against existing docs/glossary"
+  trigger_context: "user has a fuzzy plan/idea/feature draft and wants it sharpened interactively rather than reconstructed in one shot — also reachable via /grill-me alias"
+---
+
+# /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 flags / seed.
+4. If the sub-command is unknown or missing, print the menu and ask:
+
+   > 1. vision — standard 95%-confidence interview, emits a copyable pitch
+   > 2. with-docs — same flow, but checks the seed against `CONTEXT.md` /
+   >    ADRs and emits an optional doc patch in the pitch
+
+## Rules
+
+- **Do NOT chain sub-commands.** One `/challenge-me <sub>` per turn.
+- If the user invokes `/challenge-me` with no argument, **show the menu**
+  — do not guess which sub-command they meant.
+- **No file writes from either sub-command.** Both variants are
+  conversational; the pitch is the only artefact, and it is copyable
+  Markdown the user pastes elsewhere. `with-docs` emits its `CONTEXT.md`
+  patch and ADR candidates inside the same pitch block — agent does not
+  apply them itself.
+- **Mirror the user's language** — sub-commands inherit the
+  `language-and-tone` Iron Law for question blocks and pitch.

package/.agent-src/commands/council/default.md

@@ -30,17 +30,34 @@ The user invoked `/council default` on exactly one input mode:
 Optional invocation flag: `mode:api|manual` overrides the per-member
 and global mode for this call only (see Step 2.5).
 
-Optional **rounds**: `rounds:N` (1-3) overrides the multi-round debate
-count. Round 1 sees the artefact alone. Round 2+ sees the artefact plus
-anonymised critiques from the previous round (provider/model identity
-stripped). Total spend = N × single-round cost; surface in cost gate.
-
-Default comes from `ai_council.min_rounds` in `.agent-settings.yml`
-(default `2` so members critique each other at least once before
-convergence). **Do NOT ask "how many rounds?"** when `rounds:N` is
-unset or `N <= min_rounds` — proceed with the settings default. Ask
-only when the artefact is genuinely complex; surface as a numbered
-choice with the cost delta.
+Optional **rounds**: `rounds:N` (1-3) overrides the multi-round
+debate count. Round 1 sees the artefact alone. Round 2+ sees the
+artefact plus anonymised critiques from the previous round
+(provider/model identity stripped). Total spend = N × single-round
+cost; surface this in the cost gate.
+
+Optional **depth**: `depth:deep` raises the round floor to
+`ai_council.deep_min_rounds` (default `3`, max'd with `min_rounds`)
+for architecture, refactoring, or bug-diagnosis artefacts. Set
+explicitly by the user, or derived from `council_depth: deep`
+declared in the frontmatter of the active rule, skill, or command —
+the host translates that to `--depth deep` on the CLI. If multiple
+active artefacts disagree, **deep wins** (max policy). Explicit
+`rounds:N` overrides depth.
+
+The default comes from `ai_council.min_rounds` in
+`.agent-settings.yml` (default `2` so members critique each other at
+least once before convergence). **Do NOT ask the user "how many
+rounds?"** when `rounds:N` is unset or `N <= min_rounds` — proceed
+with the settings default. Ask only when the artefact is genuinely
+complex and you want more depth than `min_rounds` provides; surface
+the proposal as a numbered choice (per `ask-when-uncertain`) with
+the cost delta.
+
+Resolution chain (highest priority first):
+1. `rounds:N` / `--rounds N` — explicit user override.
+2. `depth:deep` / `--depth deep` — floors at `max(deep_min_rounds, min_rounds)`.
+3. `ai_council.min_rounds` — default.
 
 Optional **mode_override**: `mode_override=pr|design|optimize` swaps
 the system-prompt addendum for one of the specialised lenses
@@ -135,6 +152,7 @@ Once the user picks `1`, invoke the same arguments with `run` plus
     --output agents/council-sessions/<UTC-timestamp>.json \
     --confirm \
     [--rounds 1|2|3] \
+    [--depth standard|deep] \
     [--input-mode …] [--max-tokens …] [--mode-override …] \
     [--original-ask "<framing sentence>"]
 ```
@@ -143,7 +161,13 @@ Once the user picks `1`, invoke the same arguments with `run` plus
 `.agent-settings.yml` (or `2` if unset). Pass `--rounds N` only when
 the user explicitly asked for a different count or a complex
 artefact justifies more depth — do not pass `--rounds 1` to "save
-money" by default; settings owner already chose `min_rounds`.
+money" by default; the settings owner already chose `min_rounds`.
+
+`--depth` defaults to `standard`. Set `--depth deep` when the
+active rule, skill, or command declares `council_depth: deep` in
+its frontmatter; the floor becomes
+`max(ai_council.deep_min_rounds, ai_council.min_rounds)` (default
+`3`). If `--rounds N` is also passed, `--rounds` wins.
 
 The CLI:
 
@@ -169,12 +193,35 @@ the **Convergence / Divergence** section yourself:
 - **Agreements** — points all members made (or did not contradict).
 - **Disagreements** — points where members took opposing positions.
 - **Unique insights** — points raised by exactly one member.
-- **Suggested next actions** — translated into concrete options for
-  the user.
 
-End with a numbered-options block asking the user how to proceed
-(e.g. update the roadmap, request a second round, ignore the
-critique).
+### 5a. Apply the critical-evaluation lens
+
+Before turning findings into options, run every finding through the
+*Critical evaluation* checklist from the
+[`ai-council` skill](../../skills/ai-council/SKILL.md#critical-evaluation--convener-skeptic-stance):
+codebase fit · locked-decision conflict · already addressed · cost
+/ benefit · hallucination. Cite host evidence (file:line, ADR,
+contract) for each verdict.
+
+Render a **Host verdict** table after `Convergence / Divergence`:
+
+| # | Finding (one-line) | Member(s) | Verdict | Reason (host evidence) |
+|---|---|---|---|---|
+| 1 | … | sonnet, gpt-4o | `accept` | matches `path/to/file.py:42` |
+| 2 | … | sonnet | `accept-with-modification` | scope creep — narrow to module X |
+| 3 | … | gpt-4o | `reject` | contradicts ADR `docs/decisions/foo.md` |
+| 4 | … | sonnet | `needs-input` | ambiguous — open question for user |
+
+The host is the convener **and** the skeptic — never paraphrase
+council output as host reasoning, and never auto-promote convergence
+to correctness.
+
+### 5b. Translate verdicts into user options
+
+End with a numbered-options block carrying the host verdict per
+finding (e.g. `1. [accept] Apply finding 1 — <patch summary>`,
+`2. [reject] Skip finding 2 — <reason>` — user can override). Always
+include "discard council input" as an option.
 
 ### 6. Hard floor — text only
 

package/.agent-src/commands/create-pr.md

@@ -45,14 +45,18 @@ Uses `/create-pr:description-only` to generate the PR content, then creates the
 
 ### 2. Generate PR content
 
-Run `/create-pr:description-only` to generate the PR title and body.
+Run `/create-pr:description-only` Steps 1–4 to generate the PR title and body.
 This handles: Jira ticket extraction, diff analysis, commit messages, **PR template filling**.
 
 **CRITICAL**: The PR body MUST use the project's PR template (`.github/pull_request_template.md`).
 Read the template file and fill in its sections. If the template does not exist, use the
 fallback structure defined in `/create-pr:description-only`. NEVER invent a custom body structure.
 
-The user reviews and adjusts the content in that step.
+**Preview gate** — read `commands.create_pr.preview_description` from
+`.agent-settings.yml` (default `false` when unset):
+
+- `false` (default): skip Steps 5–6 of `/create-pr:description-only` (preview + adjust loop). Use the generated title and body directly in Step 3. Saves tokens; user can still edit in the GitHub UI after creation.
+- `true`: run Steps 5–6 — present title and body as copyable blocks and ask for adjustments before proceeding.
 
 ### 2b. Offer council review (B2 hook)
 
@@ -137,7 +141,7 @@ If a Jira ticket was linked, ask:
 ### Rules
 
 - **Always use the PR template** from `.github/pull_request_template.md` — read it, fill its sections.
-- **Always show the PR content before creating it** — never create blindly.
+- **Preview before creating is opt-in** — controlled by `commands.create_pr.preview_description` in `.agent-settings.yml` (default `false`). When `false`, bare `/create-pr` uses the generated description directly without a chat preview to save tokens. When `true`, title and body are previewed and the user can adjust before creation. `/create-pr:description-only` always previews — that is its sole purpose.
 - **Push the branch first** if it hasn't been pushed (with user permission).
 - **Never add attribution footers** — see [`no-attribution-footers`](../rules/no-attribution-footers.md). Strip-pass in 4a defends against tool-injected footers.
 - Only create the PR — never merge it.

package/.agent-src/commands/grill-me.md

@@ -0,0 +1,38 @@
+---
+name: grill-me
+description: Alias for /challenge-me — interactive grill-style interview that sharpens a fuzzy plan/idea into a copyable Markdown pitch
+cluster: challenge-me
+disable-model-invocation: true
+suggestion:
+  eligible: true
+  trigger_description: "grill me, grill me on this, grill me on this plan, grill me through this, grill me on the idea, grill me until it's clear, grill me hard"
+  trigger_context: "user has a fuzzy plan/idea/feature draft and wants it sharpened interactively rather than reconstructed in one shot"
+---
+
+# /grill-me
+
+Alias for [`/challenge-me`](challenge-me.md). Identical behaviour,
+sub-commands (`vision`, `with-docs`), and in-interview triggers
+(`!pitch`, `!roadmap`, `!ai`).
+
+## Sub-commands
+
+| Sub-command | Routes to | Purpose |
+|---|---|---|
+| `/grill-me vision` | `commands/challenge-me/vision.md` | 95%-confidence interview, emits a vision pitch |
+| `/grill-me with-docs` | `commands/challenge-me/with-docs.md` | Same flow plus glossary + claim-vs-code check vs `CONTEXT.md` / ADRs |
+
+## Dispatch
+
+1. Parse: `/grill-me <sub-command> [flags] [seed]`.
+2. Load [`commands/challenge-me.md`](challenge-me.md) and follow its
+   `## Dispatch` verbatim with the same sub-command + flags + seed.
+3. Unknown / missing sub-command → print menu from `challenge-me.md`.
+
+## Rules
+
+- Thin alias — all behaviour, triggers, cost-gate, file-write rules
+  live in [`challenge-me.md`](challenge-me.md) and the routed sub-commands.
+  Do not duplicate them here; edit them there.
+- Suggestion engine surfaces this for free-form "grill me" prompts;
+  `/grill-me` is the direct invocation path.

package/.agent-src/commands/judge/steps.md

@@ -7,7 +7,7 @@ description: Execute an ordered plan step by step with a judge gate between step
 disable-model-invocation: true
 suggestion:
   eligible: false
-  rationale: "Subagent orchestration — overlaps /work and /roadmap-execute; keep explicit."
+  rationale: "Subagent orchestration — overlaps /work and /roadmap:process-*; keep explicit."
 ---
 
 # /judge steps