@event4u/agent-config 1.16.0 → 1.18.0

package/.agent-src/commands/{create-pr-description.md → create-pr/description-only.md}

@@ -1,5 +1,7 @@
 ---
-name: create-pr-description
+name: create-pr:description-only
+cluster: create-pr
+sub: description-only
 skills: [git-workflow]
 description: Generate a PR description as a copyable markdown block — used standalone or by create-pr
 disable-model-invocation: true
@@ -9,7 +11,7 @@ suggestion:
   trigger_context: "PR exists or branch ready for review without description"
 ---
 
-# create-pr-description
+# /create-pr:description-only
 
 ## Input
 

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

@@ -1,5 +1,6 @@
 ---
 name: create-pr
+cluster: create-pr
 skills: [git-workflow]
 description: Create a GitHub PR with structured description from Jira ticket and code changes
 disable-model-invocation: true
@@ -9,11 +10,31 @@ suggestion:
   trigger_context: "branch is ahead of base and not yet on a PR"
 ---
 
-# create-pr
+# /create-pr
 
-Uses `/create-pr-description` to generate the PR content, then creates the PR via GitHub API.
+Top-level entry point for the `/create-pr` family. Bare `/create-pr`
+runs the full create-PR flow described below. The `:description-only`
+sub-command produces a copyable PR description without creating the PR.
 
-## Instructions
+## Sub-commands
+
+| Sub-command | Routes to | Purpose |
+|---|---|---|
+| `/create-pr` (bare) | this file (`## Default flow`) | Full flow — generate description, push, create PR |
+| `/create-pr:description-only` | `commands/create-pr/description-only.md` | Generate the PR description as a copyable markdown block, no PR creation |
+
+## Dispatch
+
+1. Parse the user's argument: `/create-pr[:<sub>] [args]`.
+2. Bare `/create-pr` → run the `## Default flow` below verbatim.
+3. `/create-pr:description-only` → load
+   `commands/create-pr/description-only.md` and follow its
+   `## Instructions` section verbatim.
+4. Unknown sub-command → print the table above and ask which one.
+
+## Default flow
+
+Uses `/create-pr:description-only` to generate the PR content, then creates the PR via GitHub API.
 
 ### 1. Check prerequisites
 
@@ -24,12 +45,12 @@ Uses `/create-pr-description` to generate the PR content, then creates the PR vi
 
 ### 2. Generate PR content
 
-Run `/create-pr-description` to generate the PR title and body.
+Run `/create-pr:description-only` 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`. NEVER invent a custom body structure.
+fallback structure defined in `/create-pr:description-only`. NEVER invent a custom body structure.
 
 The user reviews and adjusts the content in that step.
 

package/.agent-src/commands/{feature-dev.md → feature/dev.md}

@@ -1,5 +1,7 @@
 ---
-name: feature-dev
+name: feature:dev
+cluster: feature
+sub: dev
 description: Full 7-phase feature development workflow for complex features.
 skills: [laravel, php-coder]
 disable-model-invocation: true
@@ -9,20 +11,13 @@ suggestion:
   trigger_context: "long-form feature description spanning multiple components"
 ---
 
-<!-- F2-deprecation-banner -->
-> **Deprecated — use `/feature dev`.** This standalone command
-> is kept as a deprecation shim for one release cycle and routes to
-> the same instructions below. New invocations should go through the
-> `/feature` orchestrator (`commands/feature.md`).
-<!-- /F2-deprecation-banner -->
-
-# /feature-dev
+# /feature:dev
 
 > Full 7-phase feature development workflow for complex features.
 
 ## Trigger
 
-`/feature-dev {description}` or `/feature-dev` (interactive)
+`/feature:dev {description}` or `/feature:dev` (interactive)
 
 ## When to use
 

package/.agent-src/commands/{feature-explore.md → feature/explore.md}

@@ -1,5 +1,7 @@
 ---
-name: feature-explore
+name: feature:explore
+cluster: feature
+sub: explore
 skills: [laravel]
 description: Brainstorm and explore a feature idea before committing to a full plan
 disable-model-invocation: true
@@ -7,15 +9,9 @@ suggestion:
   eligible: true
   trigger_description: "brainstorm this idea, explore this feature concept"
   trigger_context: "open-ended feature idea without acceptance criteria"
-superseded_by: feature explore
-deprecated_in: "1.15.0"
 ---
 
-> ⚠️  /feature-explore is deprecated; use /feature explore instead.
-> This shim is retained for one release cycle (1.15.0 → next minor) and forwards to the same instructions below. See [`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
-
-# feature-explore
-
+# /feature explore
 ## Instructions
 
 This is a **lightweight, conversational** exploration — no structured output yet.

package/.agent-src/commands/{feature-plan.md → feature/plan.md}

@@ -1,5 +1,7 @@
 ---
-name: feature-plan
+name: feature:plan
+cluster: feature
+sub: plan
 skills: [feature-planning]
 description: Interactively plan a feature — research, discuss, and create a structured feature document
 disable-model-invocation: true
@@ -7,15 +9,9 @@ suggestion:
   eligible: true
   trigger_description: "plan this feature, create a feature spec for X"
   trigger_context: "feature idea referenced and no plan doc exists"
-superseded_by: feature plan
-deprecated_in: "1.15.0"
 ---
 
-> ⚠️  /feature-plan is deprecated; use /feature plan instead.
-> This shim is retained for one release cycle (1.15.0 → next minor) and forwards to the same instructions below. See [`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
-
-# feature-plan
-
+# /feature plan
 ## Instructions
 
 ### 1. Gather the idea

package/.agent-src/commands/{feature-refactor.md → feature/refactor.md}

@@ -1,5 +1,7 @@
 ---
-name: feature-refactor
+name: feature:refactor
+cluster: feature
+sub: refactor
 skills: [laravel, php-coder]
 description: Refine and update an existing feature plan through interactive discussion
 disable-model-invocation: true
@@ -7,15 +9,9 @@ suggestion:
   eligible: true
   trigger_description: "update the feature plan, refine the feature spec"
   trigger_context: "existing agents/features/*.md referenced in the prompt"
-superseded_by: feature refactor
-deprecated_in: "1.15.0"
 ---
 
-> ⚠️  /feature-refactor is deprecated; use /feature refactor instead.
-> This shim is retained for one release cycle (1.15.0 → next minor) and forwards to the same instructions below. See [`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
-
-# feature-refactor
-
+# /feature refactor
 ## Instructions
 
 ### 1. Find the feature

package/.agent-src/commands/{feature-roadmap.md → feature/roadmap.md}

@@ -1,5 +1,7 @@
 ---
-name: feature-roadmap
+name: feature:roadmap
+cluster: feature
+sub: roadmap
 skills: [agent-docs-writing]
 description: Generate implementation roadmap(s) from a feature plan and link them
 disable-model-invocation: true
@@ -7,15 +9,9 @@ suggestion:
   eligible: true
   trigger_description: "turn this feature into a roadmap, generate the implementation roadmap"
   trigger_context: "existing feature plan without linked roadmap"
-superseded_by: feature roadmap
-deprecated_in: "1.15.0"
 ---
 
-> ⚠️  /feature-roadmap is deprecated; use /feature roadmap instead.
-> This shim is retained for one release cycle (1.15.0 → next minor) and forwards to the same instructions below. See [`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
-
-# feature-roadmap
-
+# /feature roadmap
 ## Instructions
 
 ### 1. Find the feature
@@ -47,7 +43,7 @@ Stop.
 ### 2. Analyze the feature
 
 - Read the feature file completely.
-- Read `agents/roadmaps/template.md` for the roadmap structure.
+- Read the roadmap template at `.augment/templates/roadmaps.md` for the structure.
 - Research the codebase for affected areas mentioned in the feature.
 
 Determine how many roadmaps are needed:
@@ -185,7 +181,7 @@ What's next?
   requested them. See [`commit-policy`](../rules/commit-policy.md#never-write-commit-steps-into-roadmaps-unsolicited).
 - **Do NOT modify the feature plan** beyond updating the Roadmaps section and status.
 - **Always link roadmaps back to the feature** and vice versa.
-- **Use the roadmap template** from `agents/roadmaps/template.md`.
+- **Use the roadmap template** at `.augment/templates/roadmaps.md`.
 - **Reference specific files** in roadmap tasks — not vague descriptions.
 - **Include quality gates** (PHPStan, Rector, tests) in every phase.
 - **Research the codebase** to make tasks concrete and realistic.

package/.agent-src/commands/feature.md

@@ -18,11 +18,11 @@ commands with a single entry point + sub-command dispatch.
 
 | Sub-command | Routes to | Purpose |
 |---|---|---|
-| `/feature explore` | `feature-explore.md` | Brainstorm an idea before committing to a plan |
-| `/feature plan` | `feature-plan.md` | Interactively plan a feature, produce a structured plan doc |
-| `/feature refactor` | `feature-refactor.md` | Refine and update an existing feature plan |
-| `/feature roadmap` | `feature-roadmap.md` | Generate implementation roadmap(s) from a plan |
-| `/feature dev` | `feature-dev.md` | Full 7-phase feature development workflow (heavyweight) |
+| `/feature explore` | `commands/feature/explore.md` | Brainstorm an idea before committing to a plan |
+| `/feature plan` | `commands/feature/plan.md` | Interactively plan a feature, produce a structured plan doc |
+| `/feature refactor` | `commands/feature/refactor.md` | Refine and update an existing feature plan |
+| `/feature roadmap` | `commands/feature/roadmap.md` | Generate implementation roadmap(s) from a plan |
+| `/feature dev` | `commands/feature/dev.md` | Full 7-phase feature development workflow (heavyweight) |
 
 ## Workflow ordering
 
@@ -33,7 +33,7 @@ implementation). Use `refactor` whenever an existing plan needs an update.
 
 1. Parse the user's argument: `/feature <sub-command> [args]`.
 2. Look up the sub-command in the table above.
-3. Load the body of the corresponding `commands/feature-<sub>.md` file and
+3. Load the body of the corresponding `commands/feature/<sub>.md` file and
    follow its `## Instructions` (or `## Steps`) section verbatim.
 4. If the sub-command is unknown or missing, print the menu and ask:
 
@@ -43,12 +43,6 @@ implementation). Use `refactor` whenever an existing plan needs an update.
    > 4. roadmap — generate roadmap(s) from a plan
    > 5. dev — run the full 7-phase development workflow
 
-## Migration
-
-The 5 standalone `/feature-*` commands continue to work for one release
-cycle as deprecation shims. They emit a notice and route to the same
-content. New invocations should use `/feature <sub>`.
-
 ## Rules
 
 - **Do NOT chain sub-commands.** One `/feature <sub>` per turn — except

package/.agent-src/commands/{fix-ci.md → fix/ci.md}

@@ -1,5 +1,7 @@
 ---
-name: fix-ci
+name: fix:ci
+cluster: fix
+sub: ci
 skills: [github-ci, quality-tools]
 description: Fetch CI errors from GitHub Actions and fix them
 disable-model-invocation: true
@@ -7,15 +9,9 @@ suggestion:
   eligible: true
   trigger_description: "CI is failing, fix the GitHub Actions errors, the pipeline is red"
   trigger_context: "open PR with failing checks"
-superseded_by: fix ci
-deprecated_in: "1.15.0"
 ---
 
-> ⚠️  /fix-ci is deprecated; use /fix ci instead.
-> This shim is retained for one release cycle (1.15.0 → next minor) and forwards to the same instructions below. See [`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
-
-# fix-ci
-
+# /fix ci
 ## Instructions
 
 ### 1. Identify the failing CI run

package/.agent-src/commands/{fix-portability.md → fix/portability.md}

@@ -1,19 +1,15 @@
 ---
-name: fix-portability
+name: fix:portability
+cluster: fix
+sub: portability
 description: Find and fix project-specific references in shared .augment/ package files
 disable-model-invocation: true
 suggestion:
   eligible: false
   rationale: "Package-internal — only the event4u/agent-config repo runs this."
-superseded_by: fix portability
-deprecated_in: "1.15.0"
 ---
 
-> ⚠️  /fix-portability is deprecated; use /fix portability instead.
-> This shim is retained for one release cycle (1.15.0 → next minor) and forwards to the same instructions below. See [`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
-
-# fix-portability
-
+# /fix portability
 ## Instructions
 
 ### 1. Run the portability checker

package/.agent-src/commands/{fix-pr-bot-comments.md → fix/pr-bots.md}

@@ -1,5 +1,7 @@
 ---
-name: fix-pr-bot-comments
+name: fix:pr-bots
+cluster: fix
+sub: pr-bots
 skills: [php-coder, quality-tools]
 description: Fix and reply to bot review comments (Copilot, Augment, Greptile, etc.) on a GitHub PR
 disable-model-invocation: true
@@ -7,15 +9,9 @@ suggestion:
   eligible: true
   trigger_description: "address the Copilot/Greptile comments, fix the bot review feedback"
   trigger_context: "open PR with bot review comments unresolved"
-superseded_by: fix pr-bots
-deprecated_in: "1.15.0"
 ---
 
-> ⚠️  /fix-pr-bot-comments is deprecated; use /fix pr-bots instead.
-> This shim is retained for one release cycle (1.15.0 → next minor) and forwards to the same instructions below. See [`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
-
-# fix-pr-bot-comments
-
+# /fix pr-bots
 ## Input
 
 The user may or may not provide a PR URL.

package/.agent-src/commands/{fix-pr-developer-comments.md → fix/pr-developers.md}

@@ -1,5 +1,7 @@
 ---
-name: fix-pr-developer-comments
+name: fix:pr-developers
+cluster: fix
+sub: pr-developers
 skills: [php-coder]
 description: Fix and reply to human reviewer comments on a GitHub PR
 disable-model-invocation: true
@@ -7,15 +9,9 @@ suggestion:
   eligible: true
   trigger_description: "fix the human reviewer comments, address the developer feedback"
   trigger_context: "open PR with unresolved human-reviewer comments"
-superseded_by: fix pr-developers
-deprecated_in: "1.15.0"
 ---
 
-> ⚠️  /fix-pr-developer-comments is deprecated; use /fix pr-developers instead.
-> This shim is retained for one release cycle (1.15.0 → next minor) and forwards to the same instructions below. See [`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
-
-# fix-pr-developer-comments
-
+# /fix pr-developers
 ## Input
 
 The user may or may not provide a PR URL.

package/.agent-src/commands/{fix-pr-comments.md → fix/pr.md}

@@ -1,5 +1,7 @@
 ---
-name: fix-pr-comments
+name: fix:pr
+cluster: fix
+sub: pr
 skills: [php-coder]
 description: Fix and reply to all open review comments (bots + human reviewers) on a GitHub PR
 disable-model-invocation: true
@@ -7,16 +9,10 @@ suggestion:
   eligible: true
   trigger_description: "fix all PR review comments, resolve the review feedback"
   trigger_context: "open PR with unresolved comments (bot + human)"
-superseded_by: fix pr
-deprecated_in: "1.15.0"
 ---
 
-> ⚠️  /fix-pr-comments is deprecated; use /fix pr instead.
-> This shim is retained for one release cycle (1.15.0 → next minor) and forwards to the same instructions below. See [`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
-
-# fix-pr-comments
-
-This command runs `fix-pr-bot-comments` and `fix-pr-developer-comments` in sequence on the same PR.
+# /fix pr
+This command runs `/fix pr-bots` and `/fix pr-developers` in sequence on the same PR.
 
 ## Input
 
@@ -49,14 +45,14 @@ The chosen mode applies to **both** phases.
 
 ### Phase 1: Bot comments
 
-Follow the full `fix-pr-bot-comments` instructions (see `.augment/commands/fix-pr-bot-comments.md`).
+Follow the full `/fix pr-bots` instructions (see `commands/fix/pr-bots.md`).
 Use the already-confirmed PR and mode — do not ask again.
 
 Report when done: "Bot comments done. Continuing with reviewer comments..."
 
 ### Phase 2: Developer comments
 
-Follow the full `fix-pr-developer-comments` instructions (see `.augment/commands/fix-pr-developer-comments.md`).
+Follow the full `/fix pr-developers` instructions (see `commands/fix/pr-developers.md`).
 Use the same PR and mode.
 
 ### After both phases

package/.agent-src/commands/{fix-references.md → fix/refs.md}

@@ -1,19 +1,15 @@
 ---
-name: fix-references
+name: fix:refs
+cluster: fix
+sub: refs
 description: Find and fix broken cross-references in .augment/ and agents/ files
 disable-model-invocation: true
 suggestion:
   eligible: false
   rationale: "Package-internal — only the event4u/agent-config repo runs this."
-superseded_by: fix refs
-deprecated_in: "1.15.0"
 ---
 
-> ⚠️  /fix-references is deprecated; use /fix refs instead.
-> This shim is retained for one release cycle (1.15.0 → next minor) and forwards to the same instructions below. See [`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
-
-# fix-references
-
+# /fix refs
 ## Instructions
 
 ### 1. Run the reference checker

package/.agent-src/commands/{fix-seeder.md → fix/seeder.md}

@@ -1,5 +1,7 @@
 ---
-name: fix-seeder
+name: fix:seeder
+cluster: fix
+sub: seeder
 skills: [eloquent]
 description: Scan seeder data files for broken foreign key references — find constants used without getReference() and fix them
 disable-model-invocation: true
@@ -7,15 +9,9 @@ suggestion:
   eligible: true
   trigger_description: "the seeder is broken, foreign key errors in seeders"
   trigger_context: "seeder error output or recent edits in database/seeders/"
-superseded_by: fix seeder
-deprecated_in: "1.15.0"
 ---
 
-> ⚠️  /fix-seeder is deprecated; use /fix seeder instead.
-> This shim is retained for one release cycle (1.15.0 → next minor) and forwards to the same instructions below. See [`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
-
-# fix-seeder
-
+# /fix seeder
 Scans all `PhpDataSeeder` data files for foreign key references that use raw seeder constants
 instead of `getReference()`. Raw constants don't trigger lazy initialization of the referenced
 seeder, causing "items not available" errors when seeders run in unpredictable order.

package/.agent-src/commands/fix.md

@@ -18,13 +18,13 @@ with a single entry point + sub-command dispatch.
 
 | Sub-command | Routes to | Purpose |
 |---|---|---|
-| `/fix ci` | `fix-ci.md` | Fetch CI errors from GitHub Actions and fix them |
-| `/fix refs` | `fix-references.md` | Find and fix broken cross-references in `.augment/` and `agents/` |
-| `/fix portability` | `fix-portability.md` | Find and fix project-specific references in shared `.augment/` files |
-| `/fix seeder` | `fix-seeder.md` | Scan seeder data files for broken FK references |
-| `/fix pr` | `fix-pr-comments.md` | Fix and reply to **all** open review comments (bots + humans) |
-| `/fix pr-bots` | `fix-pr-bot-comments.md` | Fix and reply to **bot** review comments only |
-| `/fix pr-developers` | `fix-pr-developer-comments.md` | Fix and reply to **human** reviewer comments only |
+| `/fix ci` | `commands/fix/ci.md` | Fetch CI errors from GitHub Actions and fix them |
+| `/fix refs` | `commands/fix/refs.md` | Find and fix broken cross-references in `.augment/` and `agents/` |
+| `/fix portability` | `commands/fix/portability.md` | Find and fix project-specific references in shared `.augment/` files |
+| `/fix seeder` | `commands/fix/seeder.md` | Scan seeder data files for broken FK references |
+| `/fix pr` | `commands/fix/pr.md` | Fix and reply to **all** open review comments (bots + humans) |
+| `/fix pr-bots` | `commands/fix/pr-bots.md` | Fix and reply to **bot** review comments only |
+| `/fix pr-developers` | `commands/fix/pr-developers.md` | Fix and reply to **human** reviewer comments only |
 
 Sub-command names match the locked contract in
 [`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
@@ -45,12 +45,6 @@ Sub-command names match the locked contract in
    > 6. pr-bots — address bot reviewer comments only
    > 7. pr-developers — address human reviewer comments only
 
-## Migration
-
-The 7 standalone `/fix-*` commands continue to work for one release cycle as
-deprecation shims. They emit a notice and route to the same content. New
-invocations should use `/fix <sub>`.
-
 ## Rules
 
 - **Do NOT commit, push, or open a PR** unless the sub-command explicitly

package/.agent-src/commands/{do-and-judge.md → judge/on-diff.md}

@@ -1,5 +1,7 @@
 ---
-name: do-and-judge
+name: judge:on-diff
+cluster: judge
+sub: on-diff
 skills: [subagent-orchestration, verify-completion-evidence]
 description: Run a single change through an implementer→judge loop with a two-revision ceiling, then hand back to the user
 disable-model-invocation: true
@@ -8,8 +10,7 @@ suggestion:
   rationale: "Subagent orchestration — overlaps /work and judge skills; keep explicit."
 ---
 
-# do-and-judge
-
+# /judge on-diff
 ## Instructions
 
 ### 1. Confirm scope

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

@@ -0,0 +1,90 @@
+---
+name: judge:solo
+cluster: judge
+sub: solo
+skills: [subagent-orchestration]
+description: Run a standalone judge on an existing diff or code change — no implementer, no revision loop, verdict only
+disable-model-invocation: true
+suggestion:
+  eligible: false
+  rationale: "Sibling of /review-changes — eligibility routed there; keep this explicit."
+---
+
+# /judge solo
+## Instructions
+
+### 1. Identify the target
+
+The user invoked `/judge solo` on one of:
+
+- The current working-tree diff (`git diff`)
+- A specific commit range (`git diff A..B`)
+- A PR by number or URL
+- A single file or set of files
+
+Confirm the target in one sentence before proceeding. Do not silently
+assume the working tree.
+
+### 2. Gather the context
+
+Collect what the judge needs:
+
+- The diff in full
+- The original task, ticket, or PR description
+- Relevant acceptance criteria (tests, linter config, design doc)
+
+If any of these is missing and the judgment would be shallow without
+it, **stop** and ask.
+
+### 3. Resolve the judge model
+
+Read `.agent-settings.yml`:
+
+- `subagents.judge_model` → empty = one tier above session model
+
+Unknown alias → stop. Silence is not a fallback.
+
+### 4. Invoke the judge
+
+The judge reviews the diff against the task. Return one of:
+
+| Verdict  | Meaning                                      |
+|----------|----------------------------------------------|
+| `apply`  | Correct, complete, ready to land             |
+| `revise` | Specific issues listed — user decides next   |
+| `reject` | Fundamentally wrong approach                 |
+
+Unlike `/judge on-diff`, this command does **not** loop — no revision
+cycles. The verdict is the deliverable.
+
+### 5. Report
+
+```
+Mode:    judge (standalone)
+Target:  <diff | commit range | PR #N | files>
+Judge:   <resolved model>
+Verdict: apply | revise | reject
+Issues:  <numbered list if revise/reject>
+Next step: <what the user should do based on the verdict>
+```
+
+## Use this command when
+
+- A diff already exists and the user wants a second opinion
+- Reviewing someone else's PR before approving it
+- Double-checking a change before opening a PR
+- Stress-testing a refactor without committing to revisions
+
+## Do NOT
+
+- NEVER apply the diff — this command judges only
+- NEVER loop into a revision cycle — use `/judge on-diff` for that
+- NEVER run the judge on an empty diff — fail fast
+- NEVER silently fall back to the session model for the judge
+
+## See also
+
+- [`subagent-orchestration`](../skills/subagent-orchestration/SKILL.md)
+- [`/judge on-diff`](do-and-judge.md) — if a revision loop is wanted
+- [`/review-changes`](review-changes.md) — human-oriented self-review
+- [`role-contracts`](../../docs/guidelines/agent-infra/role-contracts.md#reviewer) — Reviewer mode output contract (Summary / Risks / Findings / Required actions / Verdict)

package/.agent-src/commands/{do-in-steps.md → judge/steps.md}

@@ -1,5 +1,7 @@
 ---
-name: do-in-steps
+name: judge:steps
+cluster: judge
+sub: steps
 skills: [subagent-orchestration, verify-completion-evidence]
 description: Execute an ordered plan step by step with a judge gate between steps — stops on first failed verdict
 disable-model-invocation: true
@@ -8,8 +10,7 @@ suggestion:
   rationale: "Subagent orchestration — overlaps /work and /roadmap-execute; keep explicit."
 ---
 
-# do-in-steps
-
+# /judge steps
 ## Instructions
 
 ### 1. Confirm the plan