@event4u/agent-config 1.14.0 → 1.16.0

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

@@ -73,7 +73,7 @@ Show the handoff prompt in a fenced code block and say:
   and without any persistent file.
 - [`/chat-history-resume`](chat-history-resume.md) is **pull-based**: the
   new chat reads `.agent-chat-history` from disk (written by the
-  [`chat-history`](../rules/chat-history.md) rule). Works only on the
+  [`chat-history`](../rules/chat-history-ownership.md) rule). Works only on the
   same machine and same repo, but captures more detail (every phase /
   tool call / decision the prior session logged).
 

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

@@ -75,8 +75,8 @@ RISIKO-CHECK:
 For each change:
 
 1. **Read the file** before modifying.
-2. **Make the change** using `str-replace-editor`.
-3. **Check for downstream effects** — use `codebase-retrieval` to find callers.
+2. **Make the change** with the file-edit tool available to the agent.
+3. **Check for downstream effects** — search the codebase for callers.
 4. **Update related code** if signatures or behavior changed.
 
 ### 4. Quality checks
@@ -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

@@ -1,6 +1,6 @@
 ---
 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.
+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
@@ -104,7 +104,7 @@ If the helper returned `skipped_cadence`, surface it:
 
 - The command writes through the same ownership-state machine as
   hooks — a `foreign` log triggers the
-  [`chat-history`](../rules/chat-history.md) Foreign-Prompt before any
+  [`chat-history`](../rules/chat-history-ownership.md) Foreign-Prompt before any
   append. This is intentional; the checkpoint must not silently
   hijack another session's log.
 - The `phase` payload key is required. Other keys are accepted but
@@ -117,7 +117,7 @@ If the helper returned `skipped_cadence`, surface it:
 
 ## See also
 
-- [`chat-history`](../rules/chat-history.md) — the rule defining the
+- [`chat-history`](../rules/chat-history-ownership.md) — the rule defining the
   conditional Iron Law (HOOK platforms vs CHECKPOINT/MANUAL platforms)
 - [`/chat-history`](chat-history.md) — read-only status display
 - [`/chat-history-resume`](chat-history-resume.md) — adopt + load

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

@@ -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.
 
@@ -96,7 +96,7 @@ effect — this command is scoped to the file on disk only.
 
 ## See also
 
-- [`chat-history`](../rules/chat-history.md) — the rule that writes the file
+- [`chat-history`](../rules/chat-history-ownership.md) — the rule that writes the file
 - [`/chat-history`](chat-history.md) — status inspection
 - [`/chat-history-resume`](chat-history-resume.md) — load + adopt instead of wipe
 - [`agent-settings` template](../templates/agent-settings.md) — `chat_history.*` reference

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

@@ -17,7 +17,7 @@ flow: silent summarize, adopt, merge, or replace.
 
 Use after a crashed chat, after switching tools (Augment → Claude Code),
 or when the agent showed the foreign- or returning-session prompt from
-the [`chat-history`](../rules/chat-history.md) rule and the user picked
+the [`chat-history`](../rules/chat-history-ownership.md) rule and the user picked
 "resume".
 
 ## When NOT to use
@@ -174,7 +174,7 @@ the user decides what to do next.
 
 ## See also
 
-- [`chat-history`](../rules/chat-history.md) — the rule that triggers
+- [`chat-history`](../rules/chat-history-ownership.md) — the rule that triggers
   this command via the foreign- and returning-session prompts
 - [`/chat-history`](chat-history.md) — status inspection without adopting
 - [`/chat-history-clear`](chat-history-clear.md) — wipe instead of adopt

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

@@ -12,7 +12,7 @@ suggestion:
 # /chat-history
 
 Inspect `.agent-chat-history` — the JSONL log maintained by the
-[`chat-history`](../rules/chat-history.md) rule for crash recovery.
+[`chat-history`](../rules/chat-history-ownership.md) rule for crash recovery.
 
 Shows:
 
@@ -31,7 +31,7 @@ Read-only — this command never writes to the file.
 - 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).
+  [`layered-settings`](../../docs/guidelines/agent-infra/layered-settings.md#section-aware-merge-rules).
 
 ## Steps
 
@@ -100,7 +100,7 @@ append may trigger overflow handling.
 
 ## See also
 
-- [`chat-history`](../rules/chat-history.md) — the rule that writes the file
+- [`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

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
@@ -9,23 +9,23 @@ suggestion:
 
 # check-current-md
 
-Manual runner for [`md-language-check`](../skills/md-language-check/SKILL.md).
-Use to spot-check an `.md` file the agent did not just edit, or to audit
-before opening a PR.
+Manual runner for the [`md-language-check`](../skills/md-language-check/SKILL.md)
+skill. Use to spot-check an `.md` file the agent did not just edit, or to
+audit a file before opening a PR.
 
 ## Instructions
 
 ### 1. Resolve target paths
 
-User passed paths → use those. Else default to the file currently open
-in the editor (per `personal.ide` open-file context). No file open and
-no path passed:
+If the user passed one or more paths, use those. Otherwise, default to
+the file currently open in the editor (per `personal.ide` open-file
+context). If no file is open and no path was passed:
 
 ```
 > ❌  No target file. Pass a path: /check-current-md path/to/file.md
 ```
 
-Stop.
+Stop here.
 
 ### 2. Run the checker
 
@@ -33,8 +33,11 @@ Stop.
 python3 scripts/check_md_language.py <path> [<path> …] --format json
 ```
 
-Exit codes: `0` clean, `1` violations (continue to step 3), `3`
-internal error (surface stderr, stop).
+Exit codes:
+
+- `0` → no findings; report and stop
+- `1` → findings present; continue to step 3
+- `3` → internal error; surface stderr and stop
 
 ### 3. Display findings
 
@@ -46,7 +49,7 @@ internal error (surface stderr, stop).
   Found: {count} violation(s) across {files} file(s)
 ```
 
-Per violation:
+For each violation:
 
 ```
   {file}:{line} — kind: {umlaut|de_word} — match: `{matched_text}`
@@ -57,14 +60,16 @@ Group by file when multiple files are scanned.
 
 ### 4. Classify and propose fixes
 
+For each violation, propose one of:
+
 | Cause | Proposed fix |
 |---|---|
-| German sentence in body prose | Translate to English |
+| German sentence in body prose | Translate the line to English |
 | Quoted German token used as example | Move into a labeled `DE: … · EN: …` block |
-| Meta-doc that documents trigger words | Append `<!-- md-language-check: ignore -->` to the line |
-| Intentionally bilingual but unlabeled | Reformat as labeled anchor block |
+| Meta-documentation that documents trigger words | Append `<!-- md-language-check: ignore -->` to the line |
+| Line is intentionally bilingual but unlabeled | Reformat as labeled anchor block |
 
-Summary:
+Present a summary:
 
 ```
   Proposed fixes:
@@ -76,20 +81,21 @@ Summary:
 > 3. Skip — report only
 ```
 
-Recommendation: **2 — Apply interactively** when ≥3 findings,
-**1 — Apply all fixes** for ≤2 findings or all-translation diffs.
+Recommendation: **2 — Apply interactively** when ≥3 findings, **1 —
+Apply all fixes** for ≤2 findings or when all are pure translations.
 
 ### 5. Apply fixes
 
 Edit only the source-of-truth file:
 
-- `.agent-src.uncompressed/` → edit directly
-- `.agent-src/` → edit the matching `.agent-src.uncompressed/` file,
-  then `bash scripts/compress.sh --sync`
-- `.augment/` → same as `.agent-src/` (it's a projection)
-- `agents/` → edit directly (no compression layer)
+- Path under `.agent-src.uncompressed/` → edit there directly
+- Path under `.agent-src/` → edit the matching
+  `.agent-src.uncompressed/` file instead, then run
+  `bash scripts/compress.sh --sync`
+- Path under `.augment/` → same as `.agent-src/` (it's a projection)
+- Path under `agents/` → edit directly (no compression layer)
 
-Re-run after fixes:
+After all fixes, re-run:
 
 ```bash
 python3 scripts/check_md_language.py <path> [<path> …]
@@ -97,27 +103,32 @@ python3 scripts/check_md_language.py <path> [<path> …]
 
 ### 6. Mark hashes (only if `.agent-src.uncompressed/` was edited)
 
+For each modified source file:
+
 ```bash
 python3 scripts/compress.py --mark-done "{relative_path}"
 ```
 
-Keeps `.compression-hashes.json` consistent.
+This keeps `.compression-hashes.json` consistent with the new content.
 
 ## Rules
 
-- **Never edit `.augment/` directly** — it's a generated projection
-  ([`augment-source-of-truth`](../rules/augment-source-of-truth.md))
-- **Per-line ignore marker** is reserved for meta-documentation that
-  must quote German tokens; not a generic mute
-- **Frontmatter is exempt** — checker skips it; don't try to "fix" it
-- **Do NOT commit or push** — leave the working tree to the user
+- **Never edit `.augment/` directly** — it's a generated projection.
+  Per [`augment-source-of-truth`](../rules/augment-source-of-truth.md),
+  the source is `.agent-src.uncompressed/`.
+- **Per-line ignore marker is reserved** for meta-documentation that
+  must quote German tokens; do NOT use it as a generic mute.
+- **Frontmatter is exempt** — the checker skips YAML frontmatter at
+  the head of the file; do not try to "fix" frontmatter.
+- **Do NOT commit or push** — finishing the check leaves the working
+  tree to the user.
 
 ## When NOT to use
 
 - Project content outside `.agent-src*/`, `.augment/`, or `agents/`
-  follows a different language policy
-- During autonomous edits the [`md-language-check`](../skills/md-language-check/SKILL.md)
-  skill already gates saves; this command is for **manual** spot-checks
+  follows a different language policy — do not enforce English there.
+- During autonomous edits, the [`md-language-check`](../skills/md-language-check/SKILL.md)
+  skill already gates saves; this command is for **manual** spot-checks.
 
 ## See also
 

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

@@ -11,10 +11,10 @@ suggestion:
 
 # commit-in-chunks
 
-Auto-split and commit all local changes in one go. Use when you want
-commits made without being asked to confirm each batch. Sibling of
-[`/commit`](commit.md), which waits for approval; this command skips
-that step.
+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
+approval. This command skips the approval step.
 
 Per [`autonomous-execution`](../rules/autonomous-execution.md), the
 agent does **not** commit on its own initiative — invoking this
@@ -30,29 +30,36 @@ git diff --stat
 git diff --cached --stat
 ```
 
-No uncommitted changes → report "Nothing to commit." and stop.
+If there are no uncommitted changes (staged or unstaged), report
+"Nothing to commit." and stop.
 
 ### 2. Determine the ticket number
 
-- Extract ticket ID from current branch (e.g. `feat/DEV-1234/...` → `DEV-1234`).
-- No ticket ID → omit scope: write `chore: ...` not `chore(): ...`. Do **not** ask the user.
+- Extract the ticket ID from the current branch name (e.g. `feat/DEV-1234/...`
+  → `DEV-1234`).
+- If no ticket ID is found, omit the scope from the messages — write
+  `chore: ...` not `chore(): ...`. Do **not** ask the user for one.
 
 ### 3. Analyze and split
 
-Group changed files into logical units per [`/commit`](commit.md) step 3:
+Group changed files into logical units following [`/commit`](commit.md)
+step 3 grouping rules:
 
 - Same feature / fix → one commit.
 - Migration + corresponding model/seeder → one commit.
-- Test + class under test → one commit.
-- Style-only (ECS/Rector/formatter) → separate `style:` / `chore:` commit when mixed with logic.
+- Test + the class under test → one commit.
+- Style-only changes (ECS/Rector/formatter) → separate `style:` /
+  `chore:` commit when mixed with logic changes.
 - Truly unrelated change → its own commit.
 
 Splitting rules:
-- **Do NOT split arbitrarily** — only when logically independent.
+- **Do NOT split arbitrarily** — only when the changes are logically
+  independent.
 - **Prefer fewer, coherent commits** over many tiny ones.
-- **Tests go with the code they test** unless test-only changes are large and noisy.
+- **Tests go with the code they test** unless test-only changes are
+  large and noisy.
 
-Generate messages per [`commit-conventions`](../rules/commit-conventions.md).
+Generate commit messages per [`commit-conventions`](../rules/commit-conventions.md).
 
 ### 4. Commit immediately
 
@@ -63,10 +70,13 @@ git add {files...}
 git commit -m "{message}"
 ```
 
-No "looks good?" prompt. No confirmation. User invoked the command knowing the plan would execute.
+No "looks good?" prompt. No confirmation step. The user invoked this
+command knowing the plan would be executed.
 
 ### 5. Report
 
+Show a summary:
+
 ```
 Created N commits:
 1. {sha1}  feat(DEV-1234): {summary}
@@ -80,19 +90,29 @@ Include `git log --oneline -N` output for verification.
 
 - **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 clearly part of the change (check `git status` first).
-- **Follow commit conventions** per [`commit-conventions`](../rules/commit-conventions.md).
-- **Stop on first failure** — if `git commit` fails (hook rejection, pre-commit lint error), stop, report, leave staged files for the user. Do not continue with remaining commits.
-- **No interactive prompts** — fail fast over hanging on input.
+- **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).
+- **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
+  to inspect.
+- **No interactive prompts** — fail fast over hanging waiting for
+  input.
 
 ## When NOT to use
 
-- User hasn't seen the diff and would benefit from review → use [`/commit`](commit.md).
-- Diff includes large unrelated changes the user might want to reorganise → use [`/commit`](commit.md).
-- Repo has a pre-commit hook requiring manual response → fix the hook or use `/commit`.
+- The user has not seen the diff yet and would benefit from review →
+  use [`/commit`](commit.md) instead.
+- The diff includes large unrelated changes the user might want to
+  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 rule that defines the no-ask commit default this command opts out of
-- [`commit-conventions`](../rules/commit-conventions.md) — message format
+- [`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
+  format

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

@@ -34,7 +34,8 @@ bash scripts/compress.sh --changed
 This lists only `.md` files whose source has changed since the last compression (based on
 stored SHA-256 hashes). If no files changed → you're done.
 
-If you need to see ALL files regardless of change status: `bash scripts/compress.sh --list`.
+If you need to see ALL files regardless of change status:
+`bash scripts/compress.sh --list`.
 
 ## Step 3: Compress each changed .md file
 
@@ -71,6 +72,7 @@ For each changed `.md` file:
    - Concrete validation checks
    - Gotchas based on real failure patterns
    - Anti-patterns that prevent recurring failures
+   - **Iron Law sections** — see "Iron Laws — do not touch" below
 5. **Enrich (SKILL.md files only):** During compression, also improve agent-effectiveness:
    - **Validation steps:** If a Procedure ends with a vague validation ("check if it works"),
      replace with concrete checks (expected output, commands to verify, specific conditions)
@@ -140,9 +142,39 @@ Show a summary table with per-category stats (files compressed, avg savings).
   (useful after an initial full compression or when bootstrapping the hash file).
 - A file with no stored hash is always treated as "changed".
 
+## Iron Laws — do not touch
+
+Sections under headings matching `Iron Law`, `Iron Laws`, or `The Iron Law` (any
+heading level, numbered variants like `Iron Law 1` included) are **load-bearing
+behavioral rules**. Compression rules above do **not** apply to them.
+
+For every Iron Law section in a source file:
+
+- **Copy the heading verbatim**, exact text, exact `#` level. NEVER downgrade
+  `## Iron Law` to `### Iron Law` or to inline `**Iron Law:**`.
+- **Copy the fenced code block byte-for-byte**, including capitalization, line
+  breaks, and trailing punctuation.
+- **Copy the negation clauses verbatim** — `NO X`, `NEVER Y`, `NOT Z`. These
+  are the law's exception denials; stripping them weakens the rule.
+- **Caveman the prose, keep every passage** — every paragraph, every list
+  item, and every fenced code block from the source must appear in the
+  compressed output, in order. Drop articles, shorten phrasing, primitive
+  grammar, terse cave-speak — all encouraged. What's forbidden is dropping
+  whole sentences, merging two paragraphs into one, or skipping a bullet.
+  One paragraph → one paragraph; one bullet → one bullet.
+- **No word-count budget** — compress the prose as hard as caveman style
+  allows. The check is structural (passage count), not quantitative.
+
+`scripts/check_compression.py` enforces these mechanically — `iron_law_missing`,
+`iron_law_passage_dropped`, and `iron_law_heading_downgrade` are `error`-level
+and block CI.
+
+If an Iron Law section genuinely contains filler (rare): edit the SOURCE in
+`.agent-src.uncompressed/`, not the compressed copy. Source is the truth.
+
 ## Compression quality checklist
 
-**Also apply the `preservation-guard` rule** — strongest validation, example, anti-pattern, and decision hints must survive compression.
+**Also apply the `preservation-guard` rule** — strongest validation, example, anti-pattern, and decision hints must survive compression. Iron Laws are non-negotiable.
 
 After compressing each file, verify:
 

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

@@ -0,0 +1,96 @@
+---
+name: council-design
+cluster: optimize
+skills: [ai-council]
+description: Run the council on a design document, ADR, or architecture proposal — surfaces hidden coupling, missing rollback, and sequencing risk before commitment.
+disable-model-invocation: true
+suggestion:
+  eligible: true
+  trigger_description: "council on this design, second opinion on the ADR, external review of architecture proposal"
+  trigger_context: "user has a design doc / ADR / architecture proposal and wants an external review before commitment"
+---
+
+# council-design
+
+## Instructions
+
+Specialised council mode for **design documents, ADRs, and
+architecture proposals**. Wraps `/council files:<paths>` (or
+`/council prompt:"…"`) with the `design` mode neutrality preamble that
+focuses members on architectural risk rather than line-level
+correctness.
+
+### 1. Resolve the artefact
+
+The user invoked `/council-design <path>` or `/council-design`. If no
+path was supplied, ask (one question per turn):
+
+> Which design artefact should the council review?
+>
+> 1. A file path (ADR, design doc, RFC)
+> 2. Multiple files / a directory (the bundler will gather them)
+> 3. A free-form proposal in the chat — paste it now
+
+Pick **1** or **2** → use `files:` mode of `/council`.
+Pick **3** → use `prompt:` mode of `/council`.
+
+### 2. Capture the originating ask
+
+Look for the artefact's stated goal — the first paragraph after the
+title, or a `## Goal` / `## Problem` section if present. That goal is
+the `original_ask` for the handoff preamble. If the artefact has no
+goal section, ask the user (one question per turn):
+
+> What is the goal of this design? (one sentence — used as neutral
+> framing for the council, not their analysis)
+
+### 3. Run /council with the design mode preamble
+
+Invoke the matching `/council` form:
+
+- `files:` → `/council files:<paths>` with `mode_override=design`.
+- `prompt:` → `/council prompt:"<artefact text>"` with
+  `mode_override=design`.
+
+The `design` mode addendum from `scripts/ai_council/prompts.py`
+focuses council members on:
+
+- Trust-boundary and module-coupling risk.
+- Rollback / kill-switch criteria the design omits.
+- Sequencing risk (does step N really not block step N+1?).
+- Open questions disguised as decisions.
+
+The cost gate from `/council` Step 3 still applies.
+
+### 4. Render the report
+
+Use the standard stacked + Convergence/Divergence layout. Add a
+one-line header at the top so reviewers know the lens:
+
+```
+## Council on <artefact path or "free-form proposal"> — design lens
+```
+
+### 5. Hand back to the user
+
+The council is **advisory**. Do **not** rewrite the design based on
+findings. Surface convergent + divergent points and let the user
+decide which to fold in via `/feature plan` or `/feature refactor`.
+
+### Hard floor (restated)
+
+`/council-design` produces **text only**. It does NOT edit the
+design file, open ADR PRs, or modify the codebase.
+
+## Failure modes
+
+- **No artefact resolvable** → ask once; if still empty, stop.
+- **Artefact too large** → bundler raises `BundleTooLarge`; suggest
+  splitting (`/council files:<single-file>` per section).
+
+## See also
+
+- `/council` — base orchestration entry point.
+- `/feature plan` / `/feature refactor` — where design changes get
+  written, after the council surfaces issues.
+- `ai-council` skill — neutrality guidelines.