@event4u/agent-config 1.15.0 → 1.17.0

package/.agent-src/commands/{agents-audit.md → agents/audit.md}

@@ -1,5 +1,7 @@
 ---
-name: agents-audit
+name: agents:audit
+cluster: agents
+sub: audit
 description: Audits agents/ and module agents/ directories — finds outdated docs, structural issues, duplicates, orphaned overrides, and creates an improvement roadmap.
 skills: [agents-audit, agent-docs-writing, override-management, module-management]
 disable-model-invocation: true
@@ -9,8 +11,7 @@ suggestion:
   trigger_context: "stale files under agents/ or recent edits to .augment/ without doc updates"
 ---
 
-# /agents-audit
-
+# /agents audit
 Audits all agent documentation across the project — root `agents/`, module `app/Modules/*/agents/`,
 and `agents/overrides/`.
 

package/.agent-src/commands/{agents-cleanup.md → agents/cleanup.md}

@@ -1,5 +1,7 @@
 ---
-name: agents-cleanup
+name: agents:cleanup
+cluster: agents
+sub: cleanup
 skills: [agent-docs-writing]
 description: Execute cleanup actions from an agents-audit — move, merge, delete, and update agent docs
 disable-model-invocation: true
@@ -8,15 +10,19 @@ suggestion:
   rationale: "Consumes prior audit output; only meaningful right after /agents-audit."
 ---
 
-# agents-cleanup
-
+# /agents cleanup
 ## Instructions
 
 ### 1. Check for audit roadmap
 
-- Check if `agents/roadmaps/agents-cleanup.md` exists (created by `/agents-audit`).
-- If yes → load it and show the phases.
-- If no → ask:
+Check the audit-roadmap path created by `/agents audit`:
+
+```
+agents/roadmaps/agents-cleanup.md
+```
+
+- If it exists → load it and show the phases.
+- If not → ask:
 
 ```
 ⚠️  No audit roadmap found.

package/.agent-src/commands/{agents-prepare.md → agents/prepare.md}

@@ -1,5 +1,7 @@
 ---
-name: agents-prepare
+name: agents:prepare
+cluster: agents
+sub: prepare
 skills: [agent-docs-writing]
 description: Scaffold the agents/ directory structure with all required subdirectories and .gitkeep files
 disable-model-invocation: true
@@ -8,8 +10,7 @@ suggestion:
   rationale: "One-shot project scaffolding; only run during initial setup."
 ---
 
-# agents-prepare
-
+# /agents prepare
 ## Instructions
 
 ### 1. Check project root

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

@@ -0,0 +1,46 @@
+---
+name: agents
+description: Agents-folder orchestrator — routes to audit, cleanup, prepare
+cluster: agents
+disable-model-invocation: true
+suggestion:
+  eligible: true
+  trigger_description: "audit agents folder, prepare agents structure, clean up agent docs"
+  trigger_context: "user wants to inspect, scaffold, or curate the agents/ tree"
+---
+
+# /agents
+
+Top-level orchestrator for the `/agents` family. Replaces 3 standalone
+commands with a single entry point + sub-command dispatch.
+
+## Sub-commands
+
+| Sub-command | Routes to | Purpose |
+|---|---|---|
+| `/agents audit` | `commands/agents/audit.md` | Audit `agents/` for outdated docs, duplicates, orphaned overrides |
+| `/agents cleanup` | `commands/agents/cleanup.md` | Execute cleanup actions from a prior audit |
+| `/agents prepare` | `commands/agents/prepare.md` | Scaffold the `agents/` directory structure |
+
+Sub-command names match the locked contract in
+[`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
+
+## Dispatch
+
+1. Parse the user's argument: `/agents <sub-command> [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:
+
+   > 1. audit — find outdated docs, duplicates, orphaned overrides
+   > 2. cleanup — execute actions from a prior audit
+   > 3. prepare — scaffold the agents/ tree
+
+## Rules
+
+- **Do NOT commit, push, or open a PR** unless the sub-command explicitly
+  authorizes it.
+- **Do NOT chain sub-commands.** One `/agents <sub>` per turn.
+- If the user invokes `/agents` with no argument, **show the menu** — do
+  not guess which sub-command they meant.

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

@@ -182,4 +182,4 @@ What next?
 
 ## See also
 
-- [`role-contracts`](../guidelines/agent-infra/role-contracts.md#developer) — Developer mode output contract (Goal / Plan / Changes / Tests / Open questions)
+- [`role-contracts`](../../docs/guidelines/agent-infra/role-contracts.md#developer) — Developer mode output contract (Goal / Plan / Changes / Tests / Open questions)

package/.agent-src/commands/bug-investigate.md

@@ -175,5 +175,5 @@ What's next?
 
 ## See also
 
-- [`role-contracts`](../guidelines/agent-infra/role-contracts.md#incident) — Incident mode output contract (Symptom / Reproduction / Minimal reversible change / Deferred verification / Follow-up commitment) — use when the bug is a live production issue with `break-glass: true`
-- [`role-contracts`](../guidelines/agent-infra/role-contracts.md#developer) — Developer mode output contract for non-incident bugs
+- [`role-contracts`](../../docs/guidelines/agent-infra/role-contracts.md#incident) — Incident mode output contract (Symptom / Reproduction / Minimal reversible change / Deferred verification / Follow-up commitment) — use when the bug is a live production issue with `break-glass: true`
+- [`role-contracts`](../../docs/guidelines/agent-infra/role-contracts.md#developer) — Developer mode output contract for non-incident bugs

package/.agent-src/commands/{chat-history-checkpoint.md → chat-history/checkpoint.md}

@@ -1,17 +1,17 @@
 ---
-name: chat-history-checkpoint
-description: Append a phase-boundary entry to .agent-chat-history — the CHECKPOINT fallback for platforms without a native hook surface (Augment Code IDE plugin, Cursor non-1.7+, Cline non-Mac/Linux). Cooperative gate, ~1 second to run.
+name: chat-history:checkpoint
+cluster: chat-history
+sub: checkpoint
+description: Append a phase-boundary entry to .agent-chat-history — CHECKPOINT fallback for platforms without a native hook (Augment IDE, Cursor pre-1.7, Cline non-Mac/Linux). ~1s.
 disable-model-invocation: true
 suggestion:
   eligible: true
   trigger_description: "User wants to flush a chat-history phase boundary on a CHECKPOINT-class platform (Augment IDE, Cursor < 1.7, Cline on Windows) — phrases like 'checkpoint chat history', 'log a phase boundary', 'manual chat-history append'."
   trigger_context: "chat_history.path == checkpoint AND a phase-shaped boundary just completed (decision recorded, multi-tool sequence finished, task-list item closed)."
 ---
-
 <!-- cloud_safe: noop -->
 
-# /chat-history-checkpoint
-
+# /chat-history checkpoint
 Force-append a `phase`-typed entry to `.agent-chat-history`. CHECKPOINT
 fallback for platforms without native hooks — see
 [`agents/contexts/chat-history-platform-hooks.md`](../../../agents/contexts/chat-history-platform-hooks.md)

package/.agent-src/commands/{chat-history-clear.md → chat-history/clear.md}

@@ -1,16 +1,16 @@
 ---
-name: chat-history-clear
+name: chat-history:clear
+cluster: chat-history
+sub: clear
 description: Manually delete the persistent chat-history log — asks for confirmation, optionally archives to a timestamped backup before wiping
 disable-model-invocation: true
 suggestion:
   eligible: false
   rationale: "Destructive log wipe — must be deliberate."
 ---
-
 <!-- cloud_safe: noop -->
 
-# /chat-history-clear
-
+# /chat-history clear
 Wipes `.agent-chat-history`. Use when the log is stale (wrong session),
 bloated beyond usefulness, or contains information you do not want
 persisted on disk.
@@ -24,7 +24,7 @@ touching the file, unless the file does not exist in the first place.
 - Keep the entries but re-point the header → [`/chat-history-resume`](chat-history-resume.md).
 - Disable logging entirely → set `chat_history.enabled: false` in
   `.agent-settings.yml`; see
-  [`layered-settings`](../guidelines/agent-infra/layered-settings.md#section-aware-merge-rules).
+  [`layered-settings`](../../docs/guidelines/agent-infra/layered-settings.md#section-aware-merge-rules).
   Disabling does not delete the existing file; run this command
   afterwards if you also want it gone.
 

package/.agent-src/commands/{chat-history-resume.md → chat-history/resume.md}

@@ -1,16 +1,16 @@
 ---
-name: chat-history-resume
+name: chat-history:resume
+cluster: chat-history
+sub: resume
 description: Load the persistent chat-history log into the current conversation — picks match/returning/foreign flow and supports resume, merge, replace, or continue
 disable-model-invocation: true
 suggestion:
   eligible: false
   rationale: "Explicit resume mechanic with foreign/returning state machine."
 ---
-
 <!-- cloud_safe: noop -->
 
-# /chat-history-resume
-
+# /chat-history resume
 Reconnects the current conversation with an existing `.agent-chat-history`
 file. Depending on the 4-state ownership check, it routes to the right
 flow: silent summarize, adopt, merge, or replace.

package/.agent-src/commands/chat-history/show.md

@@ -0,0 +1,107 @@
+---
+name: chat-history:show
+cluster: chat-history
+sub: show
+description: Show the status of the persistent chat-history log — file size, entry count, header fingerprint, age, and the last few entries
+disable-model-invocation: true
+suggestion:
+  eligible: false
+  rationale: "Status display only; no NL trigger distinct from 'show status'."
+---
+<!-- cloud_safe: noop -->
+
+# /chat-history show
+Inspect `.agent-chat-history` — the JSONL log maintained by the
+[`chat-history`](../rules/chat-history-ownership.md) rule for crash recovery.
+
+Shows:
+
+- Whether the file exists and whether logging is currently enabled
+- File size vs `max_size_kb`
+- Header metadata: fingerprint preview, created-at, `frequency`
+- Entry count and age of the oldest/newest entry
+- A peek at the last 3–5 entries so the user can see what was captured
+
+Read-only — this command never writes to the file.
+
+## When NOT to use
+
+- Load the log back into the conversation for context →
+  [`/chat-history resume`](chat-history-resume.md).
+- Wipe the file → [`/chat-history clear`](chat-history-clear.md).
+- Configure logging behavior → edit `.agent-settings.yml` directly
+  (`chat_history.*`); see
+  [`layered-settings`](../../docs/guidelines/agent-infra/layered-settings.md#section-aware-merge-rules).
+
+## Steps
+
+### 1. Check if enabled
+
+Read `chat_history.enabled` from `.agent-settings.yml`. If `false` or
+the section is missing, say so and stop:
+
+```
+> 📒 chat-history is disabled (chat_history.enabled = false).
+> Set it to true in .agent-settings.yml to start logging.
+```
+
+### 2. Read status via helper
+
+Run `scripts/chat_history.py status`. The helper returns a JSON object
+with `exists`, `size_bytes`, `size_kb`, `entries`, `header`, and `path`.
+
+If `exists: false`, tell the user the file has not been created yet —
+it will be created on the next agent turn that writes an entry.
+
+### 3. Read last N entries
+
+Run `scripts/chat_history.py read --last 5` (or equivalent — see the
+helper's CLI). Capture timestamps and entry types without loading the
+full file.
+
+### 4. Present the summary
+
+Render a concise report:
+
+```
+> 📒 chat-history status
+>
+> File:       .agent-chat-history  ({size_kb} KB / {max_size_kb} KB)
+> Entries:    {entries}
+> Fingerprint:{short_fp}  (session started {created_at_relative})
+> Frequency:  {frequency}
+> Overflow:   {on_overflow}
+>
+> Last entries:
+>   {ts_1}  {type_1}  {preview_1}
+>   {ts_2}  {type_2}  {preview_2}
+>   ...
+```
+
+Keep previews short (≤ 60 chars). Do not render the full entry text
+unless the user asks (avoids flooding the conversation with old log
+data, see [`token-efficiency`](../rules/token-efficiency.md)).
+
+### 5. Offer follow-ups (optional)
+
+If the file exists and the fingerprint does **not** match the current
+session, suggest `/chat-history resume` to adopt it.
+
+If the file is close to `max_size_kb` (> 80 %), mention it — the next
+append may trigger overflow handling.
+
+## Gotchas
+
+- `.agent-chat-history` is git-ignored. This command never commits.
+- The helper is the only way to read the file — do not cat or parse
+  the JSONL directly; entry shape is owned by `scripts/chat_history.py`.
+- If `exists: false` but the rule says logging is enabled, the file is
+  created lazily on the first append. That is expected — not an error.
+
+## See also
+
+- [`chat-history`](../rules/chat-history-ownership.md) — the rule that writes the file
+- [`/chat-history resume`](chat-history-resume.md) — adopt + load
+- [`/chat-history clear`](chat-history-clear.md) — wipe
+- [`agent-settings` template](../templates/agent-settings.md) — `chat_history.*` reference
+- [`scripts/chat_history.py`](../../../scripts/chat_history.py) — helper API

package/.agent-src/commands/chat-history.md

@@ -1,107 +1,51 @@
 ---
 name: chat-history
-description: Show the status of the persistent chat-history log — file size, entry count, header fingerprint, age, and the last few entries
+description: Chat-history orchestrator — routes to show, resume, clear, checkpoint
+cluster: chat-history
 disable-model-invocation: true
 suggestion:
-  eligible: false
-  rationale: "Status display only; no NL trigger distinct from 'show status'."
+  eligible: true
+  trigger_description: "show chat-history status, resume from log, clear the chat-history file, append a checkpoint entry"
+  trigger_context: "user wants to inspect, restore, wipe, or manually flush .agent-chat-history"
 ---
 
 <!-- cloud_safe: noop -->
 
 # /chat-history
 
-Inspect `.agent-chat-history` — the JSONL log maintained by the
-[`chat-history`](../rules/chat-history-ownership.md) rule for crash recovery.
+Top-level orchestrator for the `/chat-history` family. Replaces 4
+standalone commands with a single entry point + sub-command dispatch.
 
-Shows:
+## Sub-commands
 
-- Whether the file exists and whether logging is currently enabled
-- File size vs `max_size_kb`
-- Header metadata: fingerprint preview, created-at, `frequency`
-- Entry count and age of the oldest/newest entry
-- A peek at the last 3–5 entries so the user can see what was captured
+| Sub-command | Routes to | Purpose |
+|---|---|---|
+| `/chat-history show` | `commands/chat-history/show.md` | Inspect the log — size, entries, fingerprint, last entries |
+| `/chat-history resume` | `commands/chat-history/resume.md` | Adopt and load the persistent log into the current conversation |
+| `/chat-history clear` | `commands/chat-history/clear.md` | Wipe the log (with optional archival backup) |
+| `/chat-history checkpoint` | `commands/chat-history/checkpoint.md` | Append a phase-boundary entry on CHECKPOINT-class platforms |
 
-Read-only — this command never writes to the file.
+Sub-command names match the locked contract in
+[`docs/contracts/command-clusters.md`](../../docs/contracts/command-clusters.md).
 
-## When NOT to use
+## Dispatch
 
-- Load the log back into the conversation for context →
-  [`/chat-history-resume`](chat-history-resume.md).
-- Wipe the file → [`/chat-history-clear`](chat-history-clear.md).
-- Configure logging behavior → edit `.agent-settings.yml` directly
-  (`chat_history.*`); see
-  [`layered-settings`](../guidelines/agent-infra/layered-settings.md#section-aware-merge-rules).
+1. Parse the user's argument: `/chat-history <sub-command> [args]`.
+2. Look up the sub-command in the table above.
+3. Load the body of the routed file and follow its `## Instructions`
+   (or `## Steps`) section verbatim with the remaining args.
+4. If the sub-command is unknown or missing, print the table above and
+   ask:
 
-## Steps
+   > 1. show — inspect status, size, last entries
+   > 2. resume — adopt the log into the conversation
+   > 3. clear — wipe the file
+   > 4. checkpoint — append a phase-boundary entry
 
-### 1. Check if enabled
+## Rules
 
-Read `chat_history.enabled` from `.agent-settings.yml`. If `false` or
-the section is missing, say so and stop:
-
-```
-> 📒 chat-history is disabled (chat_history.enabled = false).
-> Set it to true in .agent-settings.yml to start logging.
-```
-
-### 2. Read status via helper
-
-Run `scripts/chat_history.py status`. The helper returns a JSON object
-with `exists`, `size_bytes`, `size_kb`, `entries`, `header`, and `path`.
-
-If `exists: false`, tell the user the file has not been created yet —
-it will be created on the next agent turn that writes an entry.
-
-### 3. Read last N entries
-
-Run `scripts/chat_history.py read --last 5` (or equivalent — see the
-helper's CLI). Capture timestamps and entry types without loading the
-full file.
-
-### 4. Present the summary
-
-Render a concise report:
-
-```
-> 📒 chat-history status
->
-> File:       .agent-chat-history  ({size_kb} KB / {max_size_kb} KB)
-> Entries:    {entries}
-> Fingerprint:{short_fp}  (session started {created_at_relative})
-> Frequency:  {frequency}
-> Overflow:   {on_overflow}
->
-> Last entries:
->   {ts_1}  {type_1}  {preview_1}
->   {ts_2}  {type_2}  {preview_2}
->   ...
-```
-
-Keep previews short (≤ 60 chars). Do not render the full entry text
-unless the user asks (avoids flooding the conversation with old log
-data, see [`token-efficiency`](../rules/token-efficiency.md)).
-
-### 5. Offer follow-ups (optional)
-
-If the file exists and the fingerprint does **not** match the current
-session, suggest `/chat-history-resume` to adopt it.
-
-If the file is close to `max_size_kb` (> 80 %), mention it — the next
-append may trigger overflow handling.
-
-## Gotchas
-
-- `.agent-chat-history` is git-ignored. This command never commits.
-- The helper is the only way to read the file — do not cat or parse
-  the JSONL directly; entry shape is owned by `scripts/chat_history.py`.
-- If `exists: false` but the rule says logging is enabled, the file is
-  created lazily on the first append. That is expected — not an error.
-
-## See also
-
-- [`chat-history`](../rules/chat-history-ownership.md) — the rule that writes the file
-- [`/chat-history-resume`](chat-history-resume.md) — adopt + load
-- [`/chat-history-clear`](chat-history-clear.md) — wipe
-- [`agent-settings` template](../templates/agent-settings.md) — `chat_history.*` reference
-- [`scripts/chat_history.py`](../../../scripts/chat_history.py) — helper API
+- **Do NOT commit, push, or open a PR** unless the sub-command
+  explicitly authorizes it.
+- **Do NOT chain sub-commands.** One `/chat-history <sub>` per turn.
+- If the user invokes `/chat-history` with no argument, **show the
+  menu** — do not guess which sub-command they meant.

package/.agent-src/commands/check-current-md.md

@@ -1,6 +1,6 @@
 ---
 name: check-current-md
-description: Check the currently open .md file (or a path you pass) for German content outside DE:/EN: anchor blocks — umlauts, German function words, untranslated quoted phrases. Reports findings and offers fixes.
+description: Check the open .md file (or a passed path) for German outside DE:/EN: anchor blocks — umlauts, function words, untranslated quotes. Reports and offers fixes.
 disable-model-invocation: true
 suggestion:
   eligible: false

package/.agent-src/commands/{commit-in-chunks.md → commit/in-chunks.md}

@@ -1,5 +1,7 @@
 ---
-name: commit-in-chunks
+name: commit:in-chunks
+cluster: commit
+sub: in-chunks
 skills: [git-workflow]
 description: Stage and commit all uncommitted changes in logical chunks WITHOUT confirmation — sibling of /commit for autonomous flows
 disable-model-invocation: true
@@ -9,14 +11,14 @@ suggestion:
   trigger_context: "autonomous mode active and uncommitted changes present"
 ---
 
-# commit-in-chunks
+# /commit:in-chunks
 
 Auto-split and commit all local changes in one go. Use this when you
 want commits made without being asked to confirm each batch. Sibling
-of [`/commit`](commit.md), which presents the plan and waits for
+of [`/commit`](../commit.md), which presents the plan and waits for
 approval. This command skips the approval step.
 
-Per [`autonomous-execution`](../rules/autonomous-execution.md), the
+Per [`autonomous-execution`](../../rules/autonomous-execution.md), the
 agent does **not** commit on its own initiative — invoking this
 command is the user's explicit consent to commit.
 
@@ -42,7 +44,7 @@ If there are no uncommitted changes (staged or unstaged), report
 
 ### 3. Analyze and split
 
-Group changed files into logical units following [`/commit`](commit.md)
+Group changed files into logical units following [`/commit`](../commit.md)
 step 3 grouping rules:
 
 - Same feature / fix → one commit.
@@ -59,7 +61,7 @@ Splitting rules:
 - **Tests go with the code they test** unless test-only changes are
   large and noisy.
 
-Generate commit messages per [`commit-conventions`](../rules/commit-conventions.md).
+Generate commit messages per [`commit-conventions`](../../rules/commit-conventions.md).
 
 ### 4. Commit immediately
 
@@ -88,11 +90,11 @@ Include `git log --oneline -N` output for verification.
 
 ## Rules
 
-- **Never push** — pushing remains explicit per [`scope-control`](../rules/scope-control.md#git-operations--permission-gated).
+- **Never push** — pushing remains explicit per [`scope-control`](../../rules/scope-control.md#git-operations--permission-gated).
 - **Never modify files** — only stage and commit existing changes.
 - **Do NOT add untracked files** unless they are clearly part of the
   change (check with `git status` first).
-- **Follow commit conventions** as defined in [`commit-conventions`](../rules/commit-conventions.md).
+- **Follow commit conventions** as defined in [`commit-conventions`](../../rules/commit-conventions.md).
 - **Stop on first failure** — if `git commit` fails (hook rejection,
   pre-commit lint error), stop, report the error, and do not continue
   with the remaining planned commits. Leave staged files for the user
@@ -103,16 +105,16 @@ Include `git log --oneline -N` output for verification.
 ## When NOT to use
 
 - The user has not seen the diff yet and would benefit from review →
-  use [`/commit`](commit.md) instead.
+  use [`/commit`](../commit.md) instead.
 - The diff includes large unrelated changes the user might want to
-  reorganise → use [`/commit`](commit.md).
+  reorganise → use [`/commit`](../commit.md).
 - The repo has a pre-commit hook that requires manual response → fix
   the hook or use `/commit`.
 
 ## See also
 
-- [`/commit`](commit.md) — split + present plan + wait for approval
-- [`autonomous-execution`](../rules/autonomous-execution.md) — the
+- [`/commit`](../commit.md) — split + present plan + wait for approval
+- [`autonomous-execution`](../../rules/autonomous-execution.md) — the
   rule that defines the no-ask commit default this command opts out of
-- [`commit-conventions`](../rules/commit-conventions.md) — message
+- [`commit-conventions`](../../rules/commit-conventions.md) — message
   format

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

@@ -1,5 +1,6 @@
 ---
 name: commit
+cluster: commit
 skills: [git-workflow]
 description: Stage and commit all uncommitted changes — splits into logical commits following Conventional Commits
 disable-model-invocation: true
@@ -9,9 +10,28 @@ suggestion:
   trigger_context: "git status shows uncommitted changes"
 ---
 
-# commit
+# /commit
 
-## Instructions
+Top-level entry point for the `/commit` family. Bare `/commit` runs the
+interactive split-and-confirm flow described below. The `:in-chunks`
+sub-command runs the same split logic without the confirmation prompt.
+
+## Sub-commands
+
+| Sub-command | Routes to | Purpose |
+|---|---|---|
+| `/commit` (bare) | this file (`## Default flow`) | Interactive — split, present plan, wait for approval, commit |
+| `/commit:in-chunks` | `commands/commit/in-chunks.md` | Autonomous — split and commit without confirmation |
+
+## Dispatch
+
+1. Parse the user's argument: `/commit[:<sub>] [args]`.
+2. Bare `/commit` → run the `## Default flow` below verbatim.
+3. `/commit:in-chunks` → load `commands/commit/in-chunks.md` and follow
+   its `## Instructions` section verbatim.
+4. Unknown sub-command → print the table above and ask which one.
+
+## Default flow
 
 ### 1. Detect uncommitted changes
 

package/.agent-src/commands/{context-create.md → context/create.md}

@@ -1,5 +1,7 @@
 ---
-name: context-create
+name: context:create
+cluster: context
+sub: create
 skills: [agent-docs-writing]
 description: Analyze a codebase area and create a structured context document
 disable-model-invocation: true
@@ -9,8 +11,7 @@ suggestion:
   trigger_context: "working in a module without an agents/contexts/ doc"
 ---
 
-# context-create
-
+# /context create
 ## Instructions
 
 ### 1. Ask what to document

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

@@ -1,5 +1,7 @@
 ---
-name: context-refactor
+name: context:refactor
+cluster: context
+sub: refactor
 skills: [agent-docs-writing]
 description: Analyze, update, and extend an existing context document
 disable-model-invocation: true
@@ -9,8 +11,7 @@ suggestion:
   trigger_context: "existing agents/contexts/*.md referenced in the prompt"
 ---
 
-# context-refactor
-
+# /context refactor
 ## Instructions
 
 ### 1. Find the context