npm - @event4u/agent-config - Versions diffs - 1.21.0 → 1.23.0 - Mend

@event4u/agent-config 1.21.0 → 1.23.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (130) hide show

package/.agent-src/commands/agents/cleanup.md +31 -17
package/.agent-src/commands/bug-fix.md +1 -0
package/.agent-src/commands/bug-investigate.md +1 -0
package/.agent-src/commands/challenge-me/vision.md +348 -0
package/.agent-src/commands/challenge-me/with-docs.md +333 -0
package/.agent-src/commands/challenge-me.md +61 -0
package/.agent-src/commands/commit/in-chunks.md +30 -10
package/.agent-src/commands/commit.md +46 -6
package/.agent-src/commands/compress.md +19 -13
package/.agent-src/commands/cost-report.md +120 -0
package/.agent-src/commands/council/default.md +64 -17
package/.agent-src/commands/create-pr/description-only.md +8 -0
package/.agent-src/commands/create-pr.md +99 -80
package/.agent-src/commands/feature/plan.md +13 -7
package/.agent-src/commands/grill-me.md +38 -0
package/.agent-src/commands/judge/steps.md +1 -1
package/.agent-src/commands/memory/add.md +16 -8
package/.agent-src/commands/memory/promote.md +17 -9
package/.agent-src/commands/optimize/rtk.md +16 -11
package/.agent-src/commands/prepare-for-review.md +12 -6
package/.agent-src/commands/project-analyze.md +31 -20
package/.agent-src/commands/review-changes.md +24 -15
package/.agent-src/commands/roadmap/ai-council.md +183 -0
package/.agent-src/commands/roadmap/create.md +20 -10
package/.agent-src/commands/roadmap/process-full.md +58 -0
package/.agent-src/commands/roadmap/process-phase.md +69 -0
package/.agent-src/commands/roadmap/process-step.md +57 -0
package/.agent-src/commands/roadmap.md +44 -16
package/.agent-src/commands/threat-model.md +1 -0
package/.agent-src/contexts/augment-infrastructure.md +1 -1
package/.agent-src/contexts/communication/rules-auto/slash-command-routing-policy-mechanics.md +53 -18
package/.agent-src/contexts/contracts/frugality-charter.md +57 -0
package/.agent-src/contexts/execution/roadmap-process-loop.md +125 -0
package/.agent-src/contexts/skills-and-commands.md +1 -1
package/.agent-src/rules/architecture.md +9 -0
package/.agent-src/rules/ask-when-uncertain.md +3 -13
package/.agent-src/rules/caveman-speak.md +78 -0
package/.agent-src/rules/direct-answers.md +5 -14
package/.agent-src/rules/improve-before-implement.md +1 -0
package/.agent-src/rules/invite-challenge.md +71 -0
package/.agent-src/rules/markdown-safe-codeblocks.md +6 -7
package/.agent-src/rules/no-cheap-questions.md +4 -14
package/.agent-src/rules/token-efficiency.md +5 -7
package/.agent-src/skills/adr-create/SKILL.md +197 -0
package/.agent-src/skills/adversarial-review/SKILL.md +1 -0
package/.agent-src/skills/agent-docs-writing/SKILL.md +23 -1
package/.agent-src/skills/ai-council/SKILL.md +132 -8
package/.agent-src/skills/bug-analyzer/SKILL.md +1 -0
package/.agent-src/skills/command-writing/SKILL.md +23 -0
package/.agent-src/skills/context-authoring/SKILL.md +23 -0
package/.agent-src/skills/conventional-commits-writing/SKILL.md +23 -0
package/.agent-src/skills/guideline-writing/SKILL.md +22 -0
package/.agent-src/skills/persona-writing/SKILL.md +153 -0
package/.agent-src/skills/readme-writing/SKILL.md +20 -0
package/.agent-src/skills/readme-writing-package/SKILL.md +19 -0
package/.agent-src/skills/roadmap-management/SKILL.md +7 -7
package/.agent-src/skills/roadmap-writing/SKILL.md +157 -0
package/.agent-src/skills/rule-writing/SKILL.md +22 -0
package/.agent-src/skills/script-writing/SKILL.md +226 -0
package/.agent-src/skills/skill-writing/SKILL.md +23 -0
package/.agent-src/skills/systematic-debugging/SKILL.md +22 -2
package/.agent-src/skills/technical-specification/SKILL.md +58 -1
package/.agent-src/skills/test-driven-development/SKILL.md +24 -0
package/.agent-src/skills/threat-modeling/SKILL.md +1 -0
package/.agent-src/templates/agent-settings.md +87 -3
package/.agent-src/templates/command.md +30 -9
package/.agent-src/templates/roadmaps.md +10 -2
package/.agent-src/templates/rule.md +8 -0
package/.agent-src/templates/skill.md +49 -0
package/.claude-plugin/marketplace.json +14 -2
package/AGENTS.md +3 -3
package/CHANGELOG.md +73 -0
package/README.md +5 -5
package/config/agent-settings.template.yml +22 -0
package/docs/architecture.md +4 -4
package/docs/contracts/command-clusters.md +45 -1
package/docs/customization.md +72 -0
package/docs/decisions/ADR-003-flat-cluster-subs-and-colon-syntax.md +126 -0
package/docs/decisions/INDEX.md +15 -0
package/docs/getting-started.md +2 -2
package/docs/guidelines/agent-infra/asking-and-brevity-examples.md +27 -19
package/docs/guidelines/agent-infra/carve-out-predicates.md +17 -0
package/docs/guidelines/agent-infra/mcp-request-signing.md +199 -0
package/docs/guidelines/agent-infra/naming.md +1 -1
package/docs/guidelines/agent-infra/roadmap-progress-mechanics.md +11 -4
package/package.json +1 -1
package/scripts/_lib/__init__.py +5 -0
package/scripts/_lib/script_output.py +140 -0
package/scripts/_phase2_shim_helper.py +1 -1
package/scripts/adr/regenerate_index.py +79 -0
package/scripts/ai_council/one_off_archive/2026-05/_one_off_add_quiet.py +149 -0
package/scripts/ai_council/one_off_archive/2026-05/_one_off_inject_quiet_flag.py +33 -0
package/scripts/ai_council/one_off_archive/2026-05/_one_off_measure_v2.sh +36 -0
package/scripts/ai_council/one_off_archive/2026-05/_one_off_measure_verbosity.sh +26 -0
package/scripts/ai_council/one_off_archive/2026-05/_one_off_per_task.sh +41 -0
package/scripts/ai_council/one_off_archive/2026-05/_one_off_silent_taskfiles.py +98 -0
package/scripts/check_augmentignore.py +4 -1
package/scripts/check_command_count_messaging.py +4 -1
package/scripts/check_compressed_paths.py +4 -1
package/scripts/check_council_layout.py +4 -1
package/scripts/check_council_references.py +4 -1
package/scripts/check_iron_law_prominence.py +3 -1
package/scripts/check_md_language.py +3 -1
package/scripts/check_memory_proposal.py +3 -1
package/scripts/check_public_catalog_links.py +4 -1
package/scripts/check_reply_consistency.py +8 -2
package/scripts/check_roadmap_trackable.py +4 -1
package/scripts/compile_router.py +27 -0
package/scripts/compress.py +33 -19
package/scripts/cost/budget.mjs +152 -0
package/scripts/cost/track.mjs +144 -0
package/scripts/council_cli.py +127 -10
package/scripts/first-run.sh +3 -9
package/scripts/install-hooks.sh +19 -1
package/scripts/install.py +17 -12
package/scripts/install.sh +19 -8
package/scripts/lint_examples.py +6 -2
package/scripts/lint_handoffs.py +4 -1
package/scripts/lint_load_context.py +4 -1
package/scripts/lint_roadmap_complexity.py +6 -2
package/scripts/lint_rule_interactions.py +4 -1
package/scripts/lint_rule_tiers.py +4 -1
package/scripts/measure_frugality_savings.py +164 -0
package/scripts/migrate_command_suggestions.py +2 -2
package/scripts/runtime_dispatcher.py +11 -0
package/scripts/schemas/command.schema.json +5 -0
package/scripts/schemas/rule.schema.json +5 -0
package/scripts/schemas/skill.schema.json +5 -0
package/scripts/skill_linter.py +208 -3
package/.agent-src/commands/roadmap/execute.md +0 -109

package/.agent-src/commands/project-analyze.md CHANGED Viewed

@@ -75,12 +75,15 @@ LEGACY CHECK (indicators):
 ═══════════════════════════════════════════════
 ```
-Ask the user with numbered options:
+Per `verbosity.routine_confirmations` (default `false`):
-```
-> 1. Continue with Phase 2 — architecture analysis
-> 2. Stop here — keep the overview only
-```
+- `false` → continue to Phase 2 silently (user invoked `/project-analyze`
+  for the full pass; "continue" is dominant).
+- `true` → ask:
+  ```
+  > 1. Continue with Phase 2 — architecture analysis
+  > 2. Stop here — keep the overview only
+  ```
 ### Phase 2: Architecture mapping
@@ -192,12 +195,15 @@ BUSINESS DOMAINS:
 ═══════════════════════════════════════════════
 ```
-Ask the user with numbered options:
+Per `verbosity.routine_confirmations` (default `false`):
-```
-> 1. Yes — create domain analysis files
-> 2. Skip — continue with next phase
-```
+- `false` → create domain analysis files silently (user invoked
+  `/project-analyze`; "yes, create" is dominant).
+- `true` → ask:
+  ```
+  > 1. Yes — create domain analysis files
+  > 2. Skip — continue with next phase
+  ```
 For each confirmed domain, create `agents/analysis/domains/{domain}.md` using the template
 from the `project-analyzer` skill.
@@ -226,12 +232,14 @@ SERVICE MAP:
 ═══════════════════════════════════════════════
 ```
-Ask the user with numbered options:
+Per `verbosity.routine_confirmations` (default `false`):
-```
-> 1. Yes — create API and service analysis files
-> 2. Skip — continue with next phase
-```
+- `false` → create API + service analysis files silently.
+- `true` → ask:
+  ```
+  > 1. Yes — create API and service analysis files
+  > 2. Skip — continue with next phase
+  ```
 Create:
 - `agents/analysis/api/endpoints-v1.md`
@@ -253,12 +261,15 @@ Write all remaining analysis files that haven't been created yet:
 - `agents/analysis/modules/{module}.md` — one per module
 - `agents/analysis/testing/test-map.md` — test suites, coverage, strategy
-For each file, ask with numbered options:
+Per `verbosity.routine_confirmations` (default `false`):
-```
-> 1. Create — {filename}
-> 2. Skip
-```
+- `false` → create all listed files silently (per-file picker is pure
+  noise once the user invoked `/project-analyze`).
+- `true` → for each file, ask:
+  ```
+  > 1. Create — {filename}
+  > 2. Skip
+  ```
 ### Phase 8: Gap analysis & action plan

package/.agent-src/commands/review-changes.md CHANGED Viewed

@@ -81,15 +81,22 @@ Pick dispatch mode based on diff size and environment:
 Each judge returns its own `Judge / Model / Target / Verdict /
 Issues` block in the format defined by that skill.
-### 4b. Optional external council (B3 hook)
+### 4b. Optional external council (B3 hook, verbosity-gated)
-If `.agent-settings.yml` has `ai_council.enabled: true` **and** at least
-one member is enabled, ask (in the user's language):
+Read `verbosity.offer_council_in_delivery` from `.agent-settings.yml`
+(default `false`):
-> 1. Add an external council review alongside the four internal judges? (billable)
-> 2. Skip — internal judges only
+- `false` (default): skip the prompt silently. When `ai_council.enabled:
+  true` AND at least one member enabled, emit one line: `→ council
+  skipped (set verbosity.offer_council_in_delivery: true to enable, or
+  run /council diff:<base>..<head> directly)`. Otherwise emit nothing.
+- `true`: when `ai_council.enabled: true` **and** at least one member
+  enabled, ask (in the user's language):
-Suppress when `personal.autonomy: on` (council is billable).
+  > 1. Add an external council review alongside the four internal judges? (billable)
+  > 2. Skip — internal judges only
+  Also suppress when `personal.autonomy: on` (council is billable).
 If picked **1**:
@@ -124,17 +131,19 @@ Produce one combined report:
   ask before fixing 🟡 findings, report 🟢 as suggestions
 - If all four returned `apply` → the diff is ready; report and stop
-### 7. Quality tools (optional)
-After the consolidated report, ask:
+### 7. Quality tools (verbosity-gated)
-```
-> 1. Yes — run quality tools (formatter, static analyzer, linters)
-> 2. No — review done
-```
+Per `verbosity.routine_confirmations` (default `false`):
-If yes, hand off to the project's quality workflow (e.g. `/quality-fix`
-or the equivalent configured command).
+- `false` (default) → emit `→ run /quality-fix to format + lint` as a
+  single follow-up line; do not auto-invoke. User runs explicitly.
+- `true` → ask:
+  ```
+  > 1. Yes — run quality tools (formatter, static analyzer, linters)
+  > 2. No — review done
+  ```
+  If yes, hand off to the project's quality workflow (e.g.
+  `/quality-fix` or the equivalent configured command).
 ## Backward compatibility

package/.agent-src/commands/roadmap/ai-council.md ADDED Viewed

@@ -0,0 +1,183 @@
+---
+name: roadmap:ai-council
+cluster: roadmap
+sub: ai-council
+skills: [ai-council, agent-docs-writing, roadmap-management]
+description: Challenge a roadmap with the AI council (deep tier) and refactor from convergence findings. Wraps `/council default` pinned to `--input-mode roadmap --depth deep`; patches surface as numbered options.
+disable-model-invocation: true
+council_depth: deep
+suggestion:
+  eligible: true
+  trigger_description: "council on roadmap, challenge this roadmap, stress-test the plan, refactor roadmap from council findings"
+  trigger_context: "existing agents/roadmaps/*.md the user wants reviewed before execution"
+---
+# /roadmap:ai-council
+Council-driven challenge + refactor scope of the
+[`/roadmap`](../roadmap.md) cluster. Pins the input mode to
+`roadmap` and the depth tier to `deep` (architecture / refactor
+artefact), then drives the user through applying convergence
+findings as numbered patches against the roadmap file.
+**Source of truth:** `.agent-src.uncompressed/` — never read or edit
+`.agent-src/` or `.augment/` directly.
+## Instructions
+### 1. Resolve the target roadmap
+Parse the argument as a roadmap path or filename:
+- `/roadmap:ai-council agents/roadmaps/<name>.md` — explicit path.
+- `/roadmap:ai-council <name>` — fuzzy match against
+  `agents/roadmaps/*.md`; if multiple match, list and ask
+  (one question per turn per `ask-when-uncertain`).
+- No argument → list `agents/roadmaps/*.md` and ask.
+Capture the **original ask** verbatim — the user's framing sentence
+that triggered this council run (e.g. *"review this roadmap before
+I execute it"*). This flows into `--original-ask`.
+### 2. Run the `/council default` flow with these pinned flags
+Follow [`/council default`](../council/default.md) Steps 2–4
+**verbatim**, with these arguments fixed:
+- `--input-mode roadmap`
+- `--depth deep` (this command declares `council_depth: deep` in
+  frontmatter; the host translates it into `--depth deep`)
+- `--output agents/council-responses/<roadmap-stem>-roadmap.json`
+  (overwrite if it exists; the previous run is the predecessor for
+  this iteration)
+- `--original-ask "<captured-ask>"`
+`--depth deep` floors rounds at
+`max(ai_council.deep_min_rounds, ai_council.min_rounds)` (default
+`3`). Do **not** pass `--rounds` unless the user explicitly asked
+for a different count.
+The cost gate from `/council default` Step 3 still applies — billable
+members require user confirmation **even under `personal.autonomy: on`**
+(per the deep tier surcharge — typical cost ~$0.05–0.13 vs. ~$0.02
+for the standard tier).
+### 3. Render the report
+Run `./agent-config council:render <output.json>` and write the
+**Convergence / Divergence** section per
+[`/council default § Render`](../council/default.md). Do **not** end
+with `/council default`'s generic numbered-options block — the
+refactor flow in Step 4 replaces it.
+### 4. Append a Council review block to the roadmap
+Open the roadmap file and append (do **not** overwrite existing
+content):
+```markdown
+## Council review (<UTC date>)
+<Convergence section verbatim>
+### Convergence findings
+1. **<Finding 1 title>** — <one-line summary> · trace: §<member-section>
+2. **<Finding 2 title>** — <one-line summary> · trace: §<member-section>
+…
+### Divergences (no consensus)
+- **<Topic>** — <Member A says X, Member B says Y; user decides>
+### Predecessor council trace
+`agents/council-responses/<roadmap-stem>-roadmap.json` (this run).
+```
+Run `./agent-config roadmap:progress` after the append. The block
+adds no `[ ]` checkboxes, so the dashboard counts stay flat.
+### 5. Apply the critical-evaluation lens, then surface verdicted patches
+Before drafting any patch, run every finding from Step 4 through the
+*Critical evaluation* checklist from the
+[`ai-council` skill](../../skills/ai-council/SKILL.md#critical-evaluation--convener-skeptic-stance):
+- **Codebase fit** — does the finding match the actual roadmap content, file paths, scripts, contracts cited in the roadmap? (`view` / `codebase-retrieval`)
+- **Locked-decision conflict** — does it contradict an ADR (`docs/decisions/`), a contract (`docs/contracts/`), a kernel rule, or an earlier locked decision in **this** roadmap?
+- **Already addressed** — is the finding already covered by an existing step, AC, or phase in the roadmap?
+- **Cost / benefit** — does the patch's scope vs. roadmap value clear the bar?
+- **Hallucination** — does the finding cite a file, function, phase, or step that does not exist?
+For every finding, attach a verdict — **`accept`**, **`accept-with-modification`**, **`reject`**, or **`needs-input`** — with a one-line reason citing host evidence (file:line, ADR, contract, roadmap step).
+Append a **Host verdict** sub-block under the Council review block in the roadmap:
+```markdown
+### Host verdict
+| # | Finding | Verdict | Reason |
+|---|---|---|---|
+| 1 | <one-line> | `accept` | matches `agents/roadmaps/<this>.md` Phase X step Y |
+| 2 | <one-line> | `accept-with-modification` | narrow scope to phase Z — global change contradicts AC §N |
+| 3 | <one-line> | `reject` | contradicts ADR `docs/decisions/<adr>.md` |
+| 4 | <one-line> | `needs-input` | open question — user picks below |
+```
+Then surface a single numbered-options block per [`user-interaction`](../../rules/user-interaction.md), carrying the verdict per option:
+> 1. `[accept]` Apply finding 1 — <one-line patch summary>
+> 2. `[accept-with-modification]` Apply finding 2 (modified) — <one-line patch summary + adjustment>
+> 3. `[reject]` Skip finding 3 — <one-line reason> (override available below)
+> 4. `[needs-input]` <open question for finding 4>
+> …
+> N. Apply all `accept` findings (recommended only if non-conflicting)
+> N+1. Override host verdict — apply a finding the host rejected (specify number)
+> N+2. Skip — leave Council review block + Host verdict as advisory only
+The user picks one or more numbers (`1,3,5` is allowed). Apply each selected patch via `str-replace-editor` against the roadmap, then re-run `./agent-config roadmap:progress` once at the end so the dashboard reflects the new step / AC count.
+**Verdict ≠ filter.** Every finding stays visible in the Host verdict block with its verdict and reason — the user can override at any time. The host filters its **own** recommendation; it does not hide council output.
+### 6. Hard floor — text + roadmap edits only
+`/roadmap:ai-council` may:
+- write `agents/council-responses/<…>.json`
+- append the Council review block to the named roadmap
+- apply user-picked patches to the same roadmap
+- regenerate `agents/roadmaps-progress.md`
+It does **NOT**:
+- edit any other roadmap, command, rule, or skill file
+- commit, push, or open a PR
+- run `git` beyond `git diff` (read-only)
+## Rules
+- **One roadmap per invocation.** Re-run for the next file.
+- **Critical evaluation is mandatory** — every council finding gets
+  a host verdict (`accept` / `accept-with-modification` / `reject` /
+  `needs-input`) with one-line evidence before any patch is drafted.
+  Convergence ≠ correctness; the council never saw the codebase. See
+  [`ai-council § Critical evaluation`](../../skills/ai-council/SKILL.md#critical-evaluation--convener-skeptic-stance).
+- **Decline = silence** ([`scope-control`](../../rules/scope-control.md)) —
+  if the user picks "Skip — advisory only", the Council review block
+  + Host verdict stay in the roadmap, but no patches are applied. Do
+  not re-ask the question on the same task.
+- **Cost gate is non-negotiable** — the deep tier costs more than
+  standard; confirm before every billable run, even with
+  `personal.autonomy: on`.
+- **No commit.** Patches land in the working tree only; commit
+  decisions stay with the user per
+  [`commit-policy`](../../rules/commit-policy.md).
+## See also
+- [`/roadmap`](../roadmap.md) — cluster orchestrator
+- [`/council default`](../council/default.md) — base flow this command wraps
+- [`ai-council`](../../skills/ai-council/SKILL.md) — neutrality, redaction, deep tier
+- [`scripts/council_cli.py`](../../../scripts/council_cli.py) — CLI entry point

package/.agent-src/commands/roadmap/create.md CHANGED Viewed

@@ -137,18 +137,23 @@ Regenerate `agents/roadmaps-progress.md` so the new roadmap shows up:
 Mention the new overall count to the user.
-### 8. Offer council review (B1 hook)
+### 8. Offer council review (B1 hook, verbosity-gated)
-If `.agent-settings.yml` has `ai_council.enabled: true` **and** at least
-one member is enabled (`anthropic` or `openai`), ask the user (in their
-language):
+Read `verbosity.offer_council_in_delivery` from `.agent-settings.yml`
+(default `false`):
-> 1. Run the council on this roadmap before execution? (billable)
-> 2. Skip council review
+- `false` (default): skip the prompt silently. When `ai_council.enabled:
+  true` AND at least one member enabled, emit one line: `→ council
+  skipped (set verbosity.offer_council_in_delivery: true to enable, or
+  run /council roadmap:<path> directly)`. Otherwise emit nothing.
+- `true`: when `ai_council.enabled: true` **and** at least one member
+  enabled (`anthropic` or `openai`), ask (in the user's language):
-Suppress this question entirely when `personal.autonomy: on` is set —
-council is billable, autonomous mode must not silently spend tokens
-(see `road-to-ai-council.md` Decision 3 / Q47).
+  > 1. Run the council on this roadmap before execution? (billable)
+  > 2. Skip council review
+  Also suppress when `personal.autonomy: on` (council is billable; see
+  `road-to-ai-council.md` Decision 3 / Q47).
 If the user picks **1**:
@@ -168,7 +173,12 @@ If the user picks **2** → continue.
 After saving (and any council review), ask the user (in their language) whether to start executing the roadmap immediately.
-If yes → switch to the `roadmap-execute` command workflow with the newly created file.
+If yes → switch to [`/roadmap:process-phase`](process-phase.md) with
+the newly created file (the default execution scope of the `/roadmap`
+cluster). Offer [`process-step`](process-step.md) and
+[`process-full`](process-full.md) as alternatives. The legacy
+`/roadmap execute` command was removed — autonomous execution is the
+only path now.
 ### Rules

package/.agent-src/commands/roadmap/process-full.md ADDED Viewed

@@ -0,0 +1,58 @@
+---
+name: roadmap:process-full
+cluster: roadmap
+sub: process-full
+skills: [agent-docs-writing, ai-council, roadmap-management]
+description: Autonomously process every open step across every phase of a roadmap until the file is fully closed. Largest execution scope of the /roadmap cluster — runs continuously across phase boundaries.
+disable-model-invocation: true
+suggestion:
+  eligible: true
+  trigger_description: "process the whole roadmap, finish the roadmap, komplette roadmap abarbeiten"
+  trigger_context: "existing agents/roadmaps/*.md and user wants the entire file done end-to-end"
+---
+# /roadmap:process-full
+Whole-roadmap execution scope of the [`/roadmap`](../roadmap.md)
+cluster. Same canonical loop as
+[`/roadmap:process-phase`](process-phase.md), but does **not** stop at
+phase boundaries — continues until every step is closed (or a halt
+condition fires).
+## Instructions
+Run the canonical loop in
+[`contexts/execution/roadmap-process-loop`](../../contexts/execution/roadmap-process-loop.md)
+with the **scope delta below**.
+## Scope delta
+- **Working set:** every open step across every phase, in document
+  order.
+- **Stop after:** the entire roadmap reaches `count_open == 0`, or a
+  halt condition fires (Hard-Floor, council-off + ambiguity,
+  security-sensitive, scope-out-of-roadmap, test/quality red).
+- **Phase boundary handling:** at every phase boundary, run the
+  per-phase quality pipeline when `quality_cadence: per_phase` (or
+  `per_step`). On red → stop, surface, do **not** silently roll into
+  the next phase.
+- **Final archival:** when the roadmap is fully closed, run the
+  archival check from
+  [`roadmap-process-loop § 6`](../../contexts/execution/roadmap-process-loop.md#6-final-report-and-archival).
+## Rules
+- **No silent acceleration past a halt.** Every halt condition stops
+  the run; the user resumes on the next turn.
+- **Phase quality pipeline runs at every phase boundary** when cadence
+  is `per_phase` or `per_step`. `end_of_roadmap` skips per-phase and
+  runs only at the final archival check.
+- All other rules from
+  [`process-phase § Rules`](process-phase.md#rules) apply unchanged.
+## See also
+- [`/roadmap`](../roadmap.md) — cluster orchestrator
+- [`/roadmap:process-step`](process-step.md) — single-step variant
+- [`/roadmap:process-phase`](process-phase.md) — default scope, single phase
+- [`roadmap-process-loop`](../../contexts/execution/roadmap-process-loop.md) — canonical mechanics

package/.agent-src/commands/roadmap/process-phase.md ADDED Viewed

@@ -0,0 +1,69 @@
+---
+name: roadmap:process-phase
+cluster: roadmap
+sub: process-phase
+skills: [agent-docs-writing, ai-council, roadmap-management]
+description: Autonomously process every open step in the next or current phase of a roadmap, then stop. Default execution scope of the /roadmap cluster.
+disable-model-invocation: true
+suggestion:
+  eligible: true
+  trigger_description: "process the next phase, finish this phase autonomously, eine phase abarbeiten"
+  trigger_context: "existing agents/roadmaps/*.md and user wants the next phase done end-to-end"
+---
+# /roadmap:process-phase
+Default execution scope of the [`/roadmap`](../roadmap.md) cluster.
+Sibling of [`/roadmap:process-step`](process-step.md) and
+[`/roadmap:process-full`](process-full.md). Replaces the legacy
+`/roadmap execute` (which paused for confirmation before every step).
+## Instructions
+Run the canonical loop in
+[`contexts/execution/roadmap-process-loop`](../../contexts/execution/roadmap-process-loop.md)
+with the **scope delta below**. The loop file owns roadmap discovery,
+pre-run summary, cadence resolution, commit-step pre-scan, the step
+loop with AI-council branching, halt conditions, and the archival
+check.
+## Scope delta
+- **Working set:** all open steps in the **first phase with
+  `count_open > 0`**. If every phase is closed → report "Roadmap
+  already complete." and run the archival check from
+  [`roadmap-process-loop § 6`](../../contexts/execution/roadmap-process-loop.md#6-final-report-and-archival).
+- **Stop after:** the phase boundary. Do **not** advance into the next
+  phase. Use [`/roadmap:process-full`](process-full.md) for continuous
+  execution across phases.
+- **Quality cadence at the boundary:** run the per-phase pipeline when
+  `quality_cadence: per_phase` (or `per_step`). Skip when
+  `end_of_roadmap`.
+## Rules
+- **Autonomous within the phase, never beyond.** The user picks
+  `process-step` for one step or `process-full` for the whole roadmap.
+- **No commit, push, branch, PR, tag, or bulk-destructive op** without
+  explicit permission this turn — see
+  [`commit-policy`](../../rules/commit-policy.md) and
+  [`scope-control § git-ops`](../../rules/scope-control.md#git-operations--permission-gated).
+  Roadmap-listed commit steps follow the single-upfront-ask flow in
+  [`roadmap-process-loop § 3`](../../contexts/execution/roadmap-process-loop.md#3-commit-step-pre-scan--one-upfront-ask).
+- **Every checkbox edit syncs the dashboard in the same response** per
+  [`roadmap-progress-sync`](../../rules/roadmap-progress-sync.md).
+- **AI-council consultations run silently when council is on.** No
+  per-call confirmation. The opt-in covers the whole run.
+- **Decline = silence.** Once the user said "skip council", do not
+  re-offer for the rest of this run.
+- **Halt cleanly on Hard-Floor or true ambiguity.** Surface state,
+  wait. Resume on the user's next turn from the same checkbox.
+## See also
+- [`/roadmap`](../roadmap.md) — cluster orchestrator
+- [`/roadmap:process-step`](process-step.md) — single-step variant
+- [`/roadmap:process-full`](process-full.md) — across-phases variant
+- [`/roadmap:create`](create.md) — sibling, scaffolds roadmaps
+- [`roadmap-process-loop`](../../contexts/execution/roadmap-process-loop.md) — canonical mechanics
+- [`roadmap-management`](../../skills/roadmap-management/SKILL.md) — checkbox + archival mechanics

package/.agent-src/commands/roadmap/process-step.md ADDED Viewed

@@ -0,0 +1,57 @@
+---
+name: roadmap:process-step
+cluster: roadmap
+sub: process-step
+skills: [agent-docs-writing, ai-council, roadmap-management]
+description: Autonomously process the single next open step of a roadmap and stop. Smallest execution scope of the /roadmap cluster — one step in, one step out.
+disable-model-invocation: true
+suggestion:
+  eligible: true
+  trigger_description: "process the next step, do the next roadmap step, einen schritt abarbeiten"
+  trigger_context: "existing agents/roadmaps/*.md and user wants exactly one step done autonomously"
+---
+# /roadmap:process-step
+One-step execution scope of the [`/roadmap`](../roadmap.md) cluster.
+Same canonical loop as [`/roadmap:process-phase`](process-phase.md),
+bounded to a single iteration.
+## Instructions
+Run the canonical loop in
+[`contexts/execution/roadmap-process-loop`](../../contexts/execution/roadmap-process-loop.md)
+with the **scope delta below**.
+## Scope delta
+- **Working set:** the **first checkbox `[ ]` in document order**
+  inside the first phase with `count_open > 0`. If every step is
+  closed → report "Roadmap already complete." and run the archival
+  check from
+  [`roadmap-process-loop § 6`](../../contexts/execution/roadmap-process-loop.md#6-final-report-and-archival).
+- **Stop after:** one full iteration of
+  [`roadmap-process-loop § 5`](../../contexts/execution/roadmap-process-loop.md#5-step-loop)
+  (sub-steps 1–7). After the checkbox edit + dashboard regen, **stop**.
+- **Quality cadence:** run the per-step pipeline only when
+  `quality_cadence: per_step`. Skip otherwise.
+- **Phase boundary:** if this single step happens to close the phase,
+  do **not** advance. Report the phase as complete and stop.
+- **Roadmap boundary:** if this single step happens to close the
+  entire roadmap, run the archival check before reporting.
+## Rules
+- **Stop after one step**, even if the next step is trivial. The user
+  picks `process-phase` or `process-full` when they want more.
+- All other rules from
+  [`process-phase § Rules`](process-phase.md#rules) apply unchanged:
+  Hard-Floor, no auto-commit, dashboard sync, AI-council silent-when-on,
+  decline = silence.
+## See also
+- [`/roadmap`](../roadmap.md) — cluster orchestrator
+- [`/roadmap:process-phase`](process-phase.md) — default scope, single phase
+- [`/roadmap:process-full`](process-full.md) — across-phases variant
+- [`roadmap-process-loop`](../../contexts/execution/roadmap-process-loop.md) — canonical mechanics

package/.agent-src/commands/roadmap.md CHANGED Viewed

@@ -1,44 +1,72 @@
 ---
 name: roadmap
-description: Roadmap orchestrator — routes to create, execute
+description: Roadmap orchestrator — routes to create (authoring) and process-step / process-phase / process-full (autonomous execution).
 cluster: roadmap
 disable-model-invocation: true
 suggestion:
   eligible: true
-  trigger_description: "create a roadmap, execute a roadmap, plan a roadmap interactively"
-  trigger_context: "user wants to scaffold or run a roadmap under agents/roadmaps/"
+  trigger_description: "create a roadmap, process a roadmap, work through a roadmap autonomously, plan or abarbeiten"
+  trigger_context: "user wants to scaffold or autonomously execute a roadmap under agents/roadmaps/"
 ---
 # /roadmap
-Top-level orchestrator for the `/roadmap` family. Replaces 2 standalone
-commands with a single entry point + sub-command dispatch.
+Top-level orchestrator for the `/roadmap` family. Carries authoring
+(`create`) and the three autonomous-execution scopes (`process-step`,
+`process-phase`, `process-full`). The legacy `/roadmap execute` (which
+paused for confirmation before every step) was removed —
+`process-phase` is the default execution scope.
 ## Sub-commands
 | Sub-command | Routes to | Purpose |
 |---|---|---|
-| `/roadmap create` | `commands/roadmap/create.md` | Interactively create a new roadmap in `agents/roadmaps/` |
-| `/roadmap execute` | `commands/roadmap/execute.md` | Read and interactively execute a roadmap |
+| `/roadmap:create` | `commands/roadmap/create.md` | Interactively scaffold a new roadmap in `agents/roadmaps/` |
+| `/roadmap:ai-council` | `commands/roadmap/ai-council.md` | Challenge an existing roadmap with the AI council (deep tier) and refactor from convergence findings |
+| `/roadmap:process-step` | `commands/roadmap/process-step.md` | Autonomously process the next open step, then stop |
+| `/roadmap:process-phase` (**default execution scope**) | `commands/roadmap/process-phase.md` | Autonomously process every open step in the current phase |
+| `/roadmap:process-full` | `commands/roadmap/process-full.md` | Autonomously process every open step across every phase |
 Sub-command names match the locked contract in
 [`docs/contracts/command-clusters.md`](../docs/contracts/command-clusters.md).
+`:` and space are equivalent at the cluster boundary — see
+[`slash-command-routing-policy-mechanics`](../contexts/communication/rules-auto/slash-command-routing-policy-mechanics.md#routing-semantics).
+The three `process-*` subs share the canonical loop in
+[`contexts/execution/roadmap-process-loop`](../contexts/execution/roadmap-process-loop.md);
+each only binds a scope delta.
 ## Dispatch
-1. Parse the user's argument: `/roadmap <sub-command> [args]`.
+1. Parse the user's argument: `/roadmap[:<sub>] [args]` or
+   `/roadmap <sub> [args]`.
 2. Look up the sub-command in the table above.
-3. Load the body of the routed file and follow its `## Instructions` section
-   verbatim with the remaining args.
-4. If the sub-command is unknown or missing, print the table above and ask:
+3. Load the body of the routed file and follow its `## Instructions`
+   section verbatim with the remaining args.
+4. **Legacy forwarding:**
+   - `/roadmap execute` or `/roadmap-execute` → forward to
+     [`/roadmap:process-phase`](roadmap/process-phase.md) (default
+     scope) with a one-time migration notice.
+   - `/roadmap-process[:<sub>]` (legacy top-level cluster) → forward
+     to `/roadmap:process-<sub>` with a one-time migration notice.
+5. If the sub-command is unknown or missing, print the table above
+   and ask:
    > 1. create — scaffold a new roadmap interactively
-   > 2. execute — run an existing roadmap step by step
+   > 2. ai-council — challenge + refactor an existing roadmap (deep tier)
+   > 3. process-step — process the next open step, then stop
+   > 4. process-phase — process the current phase (default)
+   > 5. process-full — process every open step across every phase
 ## Rules
-- **Do NOT commit, push, or open a PR** unless the sub-command explicitly
-  authorizes it.
+- **Do NOT commit, push, or open a PR** unless the sub-command
+  explicitly authorizes it. Roadmap-listed commit steps follow the
+  single-upfront-ask flow in
+  [`roadmap-process-loop § 3`](../contexts/execution/roadmap-process-loop.md#3-commit-step-pre-scan--one-upfront-ask).
 - **Do NOT chain sub-commands.** One `/roadmap <sub>` per turn.
-- If the user invokes `/roadmap` with no argument, **show the menu** — do
-  not guess which sub-command they meant.
+- If the user invokes `/roadmap` with no argument, **show the menu** —
+  do not guess which sub-command they meant.
+- Execution intents (*"work through the roadmap"*, *"abarbeiten"*,
+  *"finish this phase"*) default to
+  [`/roadmap:process-phase`](roadmap/process-phase.md) unless the user
+  named a different scope.

package/.agent-src/commands/threat-model.md CHANGED Viewed

@@ -3,6 +3,7 @@ name: threat-model
 skills: [threat-modeling, authz-review, security-sensitive-stop]
 description: Run a pre-implementation threat model on a proposed change — enumerates abuse cases, trust boundaries, and authorization gaps before the first line of code is written
 disable-model-invocation: true
+council_depth: deep
 suggestion:
   eligible: true
   trigger_description: "threat model this change, what could go wrong security-wise"