# Generated by scripts/generate_pack_manifests.py — DO NOT EDIT BY HAND

# Meta

Artefacts that maintain this package (agent-config itself).

- **id**: `meta`
- **version**: `5.10.1`
- **owner**: agent-config-maintainer
- **requires**: —
- **artefacts**: 263

## Commands (145)

- **`agent-handoff`** — Generate a context summary for continuing work in a fresh chat. Replaces the session system.
- **`agent-status`** — Show current conversation stats — message count, token costs, task progress, next freshness check.
- **`agents`** — Agent-layer orchestrator — routes to init, optimize, audit. Covers AGENTS.md and its multi-tool stubs (CLAUDE.md, GEMINI.md, copilot-instructions.md, .cursorrules).
- **`agents-audit`** — Audit agent infrastructure — token overhead, rule triggers, AGENTS.md health, Capability-over-Structure adherence, stale references. Read-only, suggest-only, never auto-apply.
- **`agents-init`** — Initialize the agent layer for a consumer project — creates AGENTS.md and .github/copilot-instructions.md from package templates, auto-detects stack, never leaks other projects' identifiers.
- **`agents-optimize`** — Refactor AGENTS.md to the Thin-Root contract (caps, pointer ratio, capability bullets, emergency-triage) and propagate to tool stubs. Suggest only, never auto-apply.
- **`agents-user`** — User-persona file (.agent-user.md) — interview, render, and maintain who the user is and how they want to be addressed.
- **`agents-user-accept`** — Apply a buffered observation to .agent-user.md after explicit user confirmation; bumps last_updated and drops the applied observations from the buffer.
- **`agents-user-init`** — Interactive interview that creates the project-root .agent-user.md from the locked v1 schema (name, language, role, style, voice_sample).
- **`agents-user-review`** — List buffered observations from .agent-user.observations.jsonl with numbered options to inspect or accept individually.
- **`agents-user-show`** — Read-only render of .agent-user.md — prints the persona summary the host agent loads at session start.
- **`agents-user-update`** — Open .agent-user.md in the user's IDE for manual edit; validates schema and 100-line cap on save.
- **`analytics`** — Analytics orchestrator — routes to show, prune. Local-only workspace event log under `~/.event4u/agent-config/workspace/analytics/`.
- **`analytics-prune`** — Drop events older than the 90-day retention window from the local analytics log. Atomic and idempotent.
- **`analytics-show`** — Render top prompts, launcher → completion rate per role, average session length, and knowledge-source usage from the local analytics log.
- **`analyze-reference-repo`** — Analyze an external reference repository (competitor, inspiration, peer) and produce a structured comparison + adoption plan for this project.
- **`bug-fix`** — Plan and implement a bug fix — based on investigation, with quality checks and test verification
- **`bug-investigate`** — Investigate a bug — auto-detect ticket from branch, gather Jira/Sentry/description context, trace root cause
- **`challenge-me`** — Challenge-me orchestrator — routes to vision, with-docs
- **`challenge-me-vision`** — Stress-test a plan or idea by one-question-at-a-time interview until 95% confidence — emits a copyable Markdown vision pitch for tickets, roadmaps, or fresh-chat handoff.
- **`challenge-me-with-docs`** — Doc-aware /challenge-me — 95%-confidence interview with session glossary vs CONTEXT.md, load-bearing claim-vs-code verification, optional CONTEXT.md patch + ADR candidates in the pitch.
- **`chat-history`** — Chat-history orchestrator — routes to show, import, learn
- **`chat-history-import`** — Surface prior chat-history sessions as a numbered table, let the user pick one, read it silently, and emit a short summary plus a resume offer — selective, user-driven cross-session import
- **`chat-history-learn`** — Pick a prior chat-history session and mine it for project-improving learnings — runs learning-to-rule-or-skill on the picked session, drafts proposal(s) under agents/proposals/
- **`chat-history-show`** — Show the status of the persistent chat-history log — file size, entry count, header fingerprint, age, and the last few entries
- **`check-current-md`** — 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.
- **`condense`** — Condense .md files from src/ into telegraph format and write to dist/agent-src/
- **`context`** — Context orchestrator — routes to create, refactor
- **`context-create`** — Analyze a codebase area and create a structured context document
- **`context-refactor`** — Analyze, update, and extend an existing context document
- **`cost-report`** — Capture token cost from the active Claude Code session, append to the local sessions store, and surface the 50/75/90/100% budget alert ladder with cost-profile suggestions.
- **`council`** — Council orchestrator — routes to default, pr, design, optimize, analysis, debate
- **`council-analysis`** — Run the council on a local analysis output (project-analyze, audit script, codebase scan) — critiques the analysis itself for dedup, evidence quality, and roadmap-readiness.
- **`council-debate`** — Multi-round council debate with progressive cost disclosure — each member produces a position, then rebuts the strongest opposing position in subsequent rounds. User confirms spend between rounds.
- **`council-default`** — Default council lens — neutral framing, redacted context, advisory output only. Run `/council default <input>` for prompt/roadmap/diff/files; the cluster shows a menu when invoked bare.
- **`council-design`** — Run the council on a design document, ADR, or architecture proposal — surfaces hidden coupling, missing rollback, and sequencing risk before commitment.
- **`council-optimize`** — Run the council on an optimization target — perf hot path, memory pattern, query, or an /optimize-* output — for ranked, evidence-based suggestions instead of generic advice.
- **`council-pr`** — Pull a GitHub PR via gh CLI and run the council on the diff with a PR-specific neutrality preamble — read-only by default; comment posting is opt-in.
- **`e2e-heal`** — Find, debug, and fix failing Playwright E2E tests
- **`e2e-plan`** — Explore the application and create a structured E2E test plan in Markdown
- **`estimate-ticket`** — Estimate a Jira/Linear ticket before sprint planning — size + risk + split recommendation + uncertainty, sibling to /refine-ticket, ends with a close-prompt
- **`feature`** — Feature orchestrator — routes to explore, plan, refactor, roadmap, dev
- **`feature-dev`** — Full 7-phase feature development workflow for complex features.
- **`feature-explore`** — Brainstorm and explore a feature idea before committing to a full plan
- **`feature-plan`** — Interactively plan a feature — research, discuss, and create a structured feature document
- **`feature-refactor`** — Refine and update an existing feature plan through interactive discussion
- **`feature-roadmap`** — Generate implementation roadmap(s) from a feature plan and link them
- **`fix`** — Fix orchestrator — routes to ci, references, portability, seeder, pr-comments, pr-bot-comments, pr-developer-comments
- **`fix-ci`** — Fetch CI errors from GitHub Actions and fix them
- **`fix-portability`** — Find and fix project-specific references in shared .augment/ package files
- **`fix-pr-bot-comments`** — Fix and reply to bot review comments (Copilot, Augment, Greptile, etc.) on a GitHub PR
- **`fix-pr-comments`** — Fix and reply to all open review comments (bots + human reviewers) on a GitHub PR
- **`fix-pr-developer-comments`** — Fix and reply to human reviewer comments on a GitHub PR
- **`fix-refs`** — Find and fix broken cross-references in .augment/ and agents/ files
- **`fix-seeder`** — Scan seeder data files for broken foreign key references — find constants used without getReference() and fix them
- **`ghostwriter`** — Ghostwriter cluster — fetch, write, list, show, and delete public-figure voice profiles (the third voice primitive alongside personas/ and .agent-user.md).
- **`ghostwriter-delete`** — Hard-delete a ghostwriter profile at agents/reference/ghostwriter/<slug>.md after a two-step confirmation. No backup, no soft delete — the file is gone after acceptance.
- **`ghostwriter-fetch`** — Build or refresh a public-figure voice profile under agents/reference/ghostwriter/ from a URL or bare name; runs the public-figure attestation gate; delegates web-fetch/web-search to host.
- **`ghostwriter-list`** — List captured ghostwriter profiles under agents/reference/ghostwriter/ as a numbered table with confidence, last-fetched, and stale-warning flags. Read-only.
- **`ghostwriter-show`** — Render a single ghostwriter profile in full — identity, style fingerprint, voice samples, taboos, source URLs. Read-only.
- **`ghostwriter-write`** — Draft a markdown post in the voice of a captured public-figure ghostwriter profile; appends the mandatory non-removable disclosure footer.
- **`grill-me`** — Alias for /challenge-me — interactive grill-style interview that sharpens a fuzzy plan/idea into a copyable Markdown pitch
- **`image`** — Character-image fidelity orchestrator — analyse, create, and verify a character image against its canon. Routes to analyse, create, verify.
- **`image-analyse`** — Analyse a character image down to the smallest mole and diff it against a canon — per-feature spec, OCR tattoo text, severity-ranked drift report.
- **`image-create`** — Generate a character image to spec — assemble a max-fidelity, anchors-first prompt from a Canon Spec; governance- and provider-gated, dry-run by default.
- **`image-verify`** — Verify a candidate render against its canon — run the analyser in loop mode, emit the gate verdict + remaining diff, halt-and-surface on non-pass.
- **`implement-ticket`** — Drive a ticket end-to-end through refine → memory → analyze → plan → implement → test → verify → report — Option-A loop over the `work_engine` Python engine, block-on-ambiguity, no auto-git.
- **`jira-ticket`** — Read Jira ticket from branch name, analyze linked Sentry issues, implement feature or fix bug
- **`judge`** — Judge orchestrator — routes to solo, steps, on-diff
- **`judge-on-diff`** — Run a single change through an implementer→judge loop with a two-revision ceiling, then hand back to the user
- **`judge-solo`** — Run a standalone judge on an existing diff or code change — no implementer, no revision loop, verdict only
- **`judge-steps`** — Execute an ordered plan step by step with a judge gate between steps — stops on first failed verdict
- **`knowledge`** — Knowledge orchestrator — routes to ingest, list, forget. Local-only file ingestion into the agent memory namespace.
- **`knowledge-cross-repo`** — Targeted, read-only retrieval over opted-in linked-project siblings (ADR-032 Option A). Pulls a shared type / API contract / config without bulk-including sibling files.
- **`knowledge-forget`** — Drop a knowledge ingest from `agents/memory/knowledge/` by id prefix. Atomic, no partial state. Pinning protects from LRU eviction, not from explicit forget — pinned ingests are dropped the same.
- **`knowledge-ingest`** — Walk a local path (folder, .zip, single file), redact PII + secrets, chunk to 2 KB markdown, and persist into the agent memory namespace under `knowledge/<ingest-id>/`.
- **`knowledge-list`** — List existing knowledge ingests in `agents/memory/knowledge/` (table or JSON); pin / unpin by id prefix to control LRU eviction.
- **`memory`** — Memory orchestrator — routes to add, load, mine-session, promote, propose
- **`memory-add`** — Interactively add a validated entry to an engineering-memory file (domain-invariants, architecture-decisions, incident-learnings, product-rules)
- **`memory-learn-low-impact`** — Preview validated low-impact entries that would be upstreamed to the package seed (default `--preview`); `--apply` opens a draft PR via `upstream-contribute` after re-redaction.
- **`memory-load`** — Load ALL curated entries of a given memory type into the current context — opt-in full load for deep analysis, never auto-triggered
- **`memory-mine-session`** — Mine the active session transcript for memory signals (corrections, preferences, decisions, recurring patterns) — preview-by-default, opt-in transcript access, host-agnostic via TranscriptAdapter.
- **`memory-promote`** — Promote an intake signal (or provisional proposal) into a curated memory entry — opens a PR and runs the admission gate.
- **`memory-propose`** — Append a provisional memory signal to the intake stream — the universal fallback for any producer (human or agent) to record a finding without committing to a curated entry.
- **`mode`** — Set the active role mode — prints the contract, lists default skills, and refuses work outside the contract (see role-contracts)
- **`module`** — Module orchestrator — routes to create, explore
- **`module-create`** — Create a new module from .module-template with interactive setup
- **`module-explore`** — Explore a module — load its structure, docs, and context into the current conversation
- **`optimize`** — Optimize orchestrator — routes to skills, agents-dir, augmentignore, rtk-filters
- **`optimize-agents-dir`** — Manage the agents/ directory — scaffold, folder-audit, fix. Single command with three modes (--scaffold / --audit / --fix); default = interactive wizard.
- **`optimize-augmentignore`** — Creates or updates .augmentignore based on the project's actual tech stack, large files, generated artifacts, and irrelevant agent skills/rules.
- **`optimize-prompt`** — Optimize a raw prompt for ChatGPT, Claude, Gemini, or another AI via the 4-D methodology — BASIC vs DETAIL auto-detect, one clarifying question per turn, returns the polished prompt.
- **`optimize-rtk`** — Create or optimize project-local rtk filters based on the actual toolchain
- **`optimize-skills`** — Audits skills — measures baseline, finds duplicates/merge candidates, runs linter. Suggest only, never auto-apply.
- **`orchestrate`** — Run a YAML pipeline defined under `.agent-config/orchestrations/` — chains personas / skills / commands / sub-agents per the orchestration-dsl-v1 contract
- **`override`** — Override orchestrator — routes to create, manage
- **`override-create`** — Creates a project-level override for a shared skill, rule, or command.
- **`override-manage`** — Reviews, updates, and refactors existing project-level overrides.
- **`package-reset`** — /package-reset
- **`package-test`** — /package-test
- **`post-as`** — Consumer-facing write entry points — :me drafts in the maintainer's own voice from .agent-user.md (no disclosure); :ghostwriter is a thin alias for /ghostwriter:write (mandatory disclosure footer).
- **`post-as-ghostwriter`** — Thin alias for /ghostwriter:write — drafts a copyable markdown post in a captured public-figure voice with the mandatory non-removable disclosure footer.
- **`post-as-me`** — Draft a copyable markdown post in the maintainer's own voice (style source = .agent-user.md.voice_sample). No disclosure footer — the user is the author.
- **`prepare-for-review`** — Prepare a PR branch for local review — updates main and merges the full branch chain so the branch is up to date
- **`profile`** — Session-profile orchestrator — activate / deactivate / show the active packs for this session (recommendation-bias surface filter, no persistence)
- **`profile-activate`** — Activate a session profile — surface only the named profile/pack closure plus core artefacts, no persistence
- **`profile-deactivate`** — Deactivate the session profile — clear the overlay (or drop named packs) so the full surface returns
- **`profile-show`** — Show the active session profile — active packs and surfaced/hidden command+skill counts (observability surface)
- **`project-analyze`** — Full project analysis — detect stack, inventory modules, audit docs, create missing contexts
- **`project-health`** — Quick project health check — show status of docs, modules, contexts, and roadmaps without creating anything
- **`quality-fix`** — Run quality pipeline (PHP and/or JS/TS) and fix all errors — auto-detects language from changed files
- **`refine-ticket`** — Refine a Jira/Linear ticket before planning — rewritten ticket + Top-5 risks + persona voices, orchestrates validate-feature-fit and threat-modeling, ends with a close-prompt
- **`research`** — Preliminary research scaffolder — pick objects, define fields, emit `outline.yaml` + `fields.yaml` for downstream deep research. Use for surveys, benchmarks, tech selection, competitive scans.
- **`research-deep`** — Read `outline.yaml`, research each item in batches, write per-item JSON validated against the project-local research-schema. No Python runtime, no `~/.claude/` paths.
- **`research-report`** — Summarise per-item JSON results from `/research:deep` into `report.md`. Agent renders directly + emits an optional `jq` template for deterministic regeneration. No Python runtime.
- **`review-changes`** — Self-review local changes before creating a PR — dispatches to five specialized judges (bug, security, tests, quality, architecture) and consolidates verdicts
- **`review-routing`** — Compute reviewer roles and matched historical bug patterns for the current diff, using project-local ownership-map.yml and historical-bug-patterns.yml
- **`roadmap`** — Roadmap orchestrator — routes to create (authoring) and process-step / process-phase / process-full (autonomous execution).
- **`roadmap-ai-council`** — 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.
- **`roadmap-create`** — Interactively create a new roadmap file in agents/roadmaps/
- **`roadmap-process-full`** — 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.
- **`roadmap-process-phase`** — Autonomously process every open step in the next or current phase of a roadmap, then stop. Default execution scope of the /roadmap cluster.
- **`roadmap-process-step`** — 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.
- **`rule-compliance-audit`** — Audit rule trigger quality, simulate activation, detect overlaps, and find never-activating rules
- **`set-cost-profile`** — Change the rule_loading_tier in .agent-settings.yml — shows each profile's meaning and applies the selection
- **`skill`** — Single-skill orchestrator — routes to preview. Non-destructive "what will this skill do?" before you run it.
- **`skill-preview`** — Non-destructive preview of a skill — its declared steps, execution type, allowed tools, and file/command targets — before you run it. Read-only, no execution.
- **`skills`** — Skill discovery orchestrator — routes to discover. Local, explained skill recommendations over the catalog + role shortlists + optional local analytics.
- **`skills-discover`** — Recommend skills for a role — ranked by four explained classes (most-useful-for-role, related-to-current-task, recently-adopted, popular-in-role). Local-only; every result carries a why.
- **`sync-agent-settings`** — Sync `.agent-settings.yml` against the current template + profile — adds new sections/keys, preserves user values, shows a diff before writing
- **`sync-gitignore`** — Sync the `event4u/agent-config` block in the consumer project's .gitignore — adds missing entries, preserves user-added lines, shows a diff before writing
- **`sync-gitignore-fix`** — Scrub legacy pre-`/agents/` patterns from the consumer's .gitignore (inside or outside the managed block) and re-sync the canonical entries
- **`tests`** — Tests orchestrator — routes to create, execute
- **`tests-create`** — Write meaningful tests for the current branch — stack-adaptive (pest / phpunit / vitest / jest / pytest / …)
- **`tests-execute`** — Run the project's test suite — stack-adaptive (pest / phpunit / vitest / jest / pytest / …)
- **`threat-model`** — 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
- **`update-form-request-messages`** — Sync the messages() method of a FormRequest class — add missing entries, link them to language keys, and clean up stale ones.
- **`upstream-contribute`** — Contribute a learning, skill, rule, or fix from a consumer project back to the shared agent-config package
- **`video`** — Video-creation orchestrator — Hollywood-level AI video pipeline. Routes to from-script, from-song, scene, storyboard, stitch.
- **`video-from-script`** — Drive a script end-to-end through the AI video pipeline — scenes → blueprint → image → operator pick → motion → video → stitch. Preview default; --mode commit spends behind the cost gate.
- **`video-from-song`** — Music-video from a song + reference images — accept or derive a timed scene script, optional character-lock, render, stitch, mux song as master track. Preview default; --mode commit gates the spend.
- **`video-scene`** — Render a single scene from a one-line idea — scene-expander → blueprint → image → operator pick → motion → video. Preview mode default (no spend); --mode commit renders live behind the cost gate.
- **`video-stitch`** — Re-stitch existing clips in `<project>/scenes/*/` after operator edits — no re-render. ffmpeg concat driven by manifest.json.
- **`video-storyboard`** — Image-only storyboard — script → scenes → blueprint → image render → contact-sheet PNG via ffmpeg montage. No video calls.
- **`work`** — Drive a free-form prompt end-to-end through refine → score → plan → implement → test → verify → report — Option-A loop over the `work_engine` Python engine, confidence-band gated, no auto-git.

## Rules (59)

- **`agent-authority`** — Priority Index for the four authority rules — Hard Floor → Permission Gate → Commit Default → Trivial-vs-Blocking; read first, route to canonical rule
- **`analysis-skill-routing`** — When choosing an analysis skill, route to the narrowest matching skill instead of defaulting to broad analysis
- **`architecture`** — Architecture rules for new files, classes, controllers, modules, or structural decisions about project organization
- **`artifact-drafting-protocol`** — Creating a new skill/rule/command/guideline or significantly rewriting one — runs mandatory Understand → Research → Draft first
- **`artifact-engagement-recording`** — After a /implement-ticket or /work phase-step or full task — emit one telemetry:record call
- **`ask-when-uncertain`** — Ask when uncertain — don't guess, assume, or improvise
- **`augment-edit-discipline`** — Editing .augment/ or src/ — keep files project-agnostic; sync counts and cross-refs on add/rename/delete
- **`autonomous-execution`** — Whether to ask or act on a workflow step — trivial-vs-blocking, autonomy opt-in, commit default; Hard Floor non-destructive-by-default
- **`cli-output-handling`** — Running verbose CLI output — git, tests, linters, docker, build tools, artisan, npm, composer. Wrap with rtk; tail/grep fallback
- **`command-suggestion-policy`** — Prompt without /command matching an eligible slash command — surface matches as numbered options with as-is escape; never auto-executes
- **`context-hygiene`** — Debugging, fixing errors, or long conversations — 3-failure stop rule, tool-loop detection, fresh-chat triggers
- **`copilot-routing`** — Configuring GitHub Copilot — copilot-instructions.md, PR-review patterns, suggestion behavior — route to copilot-config
- **`devcontainer-routing`** — Wiring DevContainers/Codespaces — devcontainer.json, images, VS Code features, port forwarding — route to the devcontainer skill
- **`direct-answers`** — Always — direct, unembellished answers. No flattery, no invented facts (verify load-bearing claims, otherwise ask). Emojis only as functional markers. Brevity is the default.
- **`domain-adoption-policy`** — Adopting a new domain track (mobile, ML, blockchain, IoT) — gates import on demand, ownership, CI fit, Sunset compat BEFORE harvest
- **`domain-safety-disclaimer`** — Advisory content (legal, medical, financial, consulting) — require matching 'not X advice' disclaimer; refuse diagnosis/dosage outright
- **`domain-safety-pii`** — Drafts, logs, exports touching real customer/candidate data — redact direct IDs, use placeholders, flag re-identification on quasi-IDs
- **`domain-safety-retention`** — Data retention (finance, support/CRM) — name jurisdiction gap, default to longest floor, honor DSR/audit holds, never delete under inquiry
- **`external-reference-deep-dive`** — User names external repo/file/URL/artifact as reference — fetch the actual tree and inspect, never summarize from README or metadata
- **`fast-path-marker-visibility`** — Low-impact council fast-path dispatch — host MUST surface transparency marker verbatim in reply opening; never paraphrase
- **`framework-neutrality-in-generic-skills`** — Editing a generic skill/rule/command — block single-stack mandates; use language-agnostic procedures with carve-out pointers
- **`guidelines`** — Writing or reviewing code — check relevant guideline before writing or reviewing code
- **`invite-challenge`** — Before executing a complex plan or non-trivial design — ask 'am I solving the right problem?' and pause for user confirmation
- **`language-and-tone`** — Language and tone — informal German Du, English code comments, .md files always English
- **`low-impact-corpus-privacy-floor`** — Writing/editing/upstreaming entries in agents/decisions/low-impact-decisions.md — non-bypassable privacy floor for the learning corpus
- **`markdown-safe-codeblocks`** — Generating markdown with code blocks — prevent broken nesting
- **`media-governance-routing`** — Generating AI video/image/voice — surface project-local media policies (likeness, style, public-figures, voice-cloning, disclosure)
- **`media-sync-ground-truth`** — Audio-synced video (lip-sync, beat-cuts, music video) — derive timing + singer from the transcribed real audio, never a planning doc; sign off the vocal map before any paid render
- **`missing-tool-handling`** — CLI tool needed for the task is not installed — ask before working around it; do NOT install silently
- **`model-recommendation`** — Starting a task, switching type, or invoking a skill/command that declares a model_tier — switch (Claude) or suggest (any agent) the right capability tier
- **`no-attribution-footers`** — Generating PR/issue/comment/commit bodies — forbids 'Generated with', 'Co-authored by', 'Pull Request opened by' attribution footers
- **`no-cheap-questions`** — No cheap questions — never ask what context answers, never offer Iron-Law-violating options, never stage no-trade-off choices; mode-independent (off / auto / on)
- **`no-decorative-emojis-in-git-surfaces`** — Generating PR/issue/commit titles or PR/issue comments — forbids decorative emojis; allowed in PR/issue descriptions + commit bodies only when matched by an in-artifact legend
- **`no-pr-progress-comments`** — Posting comments on an open PR — refuses unsolicited progress / status / CI-fix narration unless personal.pr_progress_comments is true
- **`no-roadmap-references`** — Linking transient files (agents/roadmaps/, agents/runtime/council/*/) from a stable artifact — both layers expire; promote findings
- **`onboarding-gate`** — First turn — if onboarding.onboarded is false in .agent-settings.yml, instruct dev to run `agent-config setup` before any request
- **`package-ci-checks`** — Before pushing to remote or creating a PR in the agent-config package — run all CI checks locally first
- **`persona-governance`** — Creating/editing/proposing personas — enforce per-domain cap (≤ 2 specialists), ≥ 1 skill citation, deprecation path
- **`preservation-guard`** — Merging/refactoring/condensing skills, rules, commands, or guidelines — prevent quality loss
- **`provider-lifecycle-discipline`** — Editing an AI video/image/audio adapter — declare lifecycle tier (experimental | stable | deprecated | community); never default to non-stable
- **`reviewer-awareness`** — Suggesting reviewers or flagging risk hotspots — anchor in paths/risk + ownership-map + bug-patterns; medium/high needs primary + secondary
- **`roadmap-ci-steps-policy`** — Authoring or executing roadmaps — forbid task ci / make test / npm run check steps when quality.local_auto_run is false; skip inline
- **`roadmap-progress-sync`** — Any roadmap touch (file move, checkbox flip, phase change) regens dashboard same response; archive at 0 open
- **`role-mode-adherence`** — When roles.active_role is set — closing outputs must match mode contract and emit structured mode marker
- **`rule-type-governance`** — Creating/editing rules, or auditing rule types — decides when a rule should be always vs auto
- **`runtime-safety`** — Skill declares execution metadata — enforce safety constraints for assisted/automated execution types
- **`size-enforcement`** — Creating or editing rules, skills, commands, guidelines, AGENTS.md, or copilot-instructions.md — enforce size and scope limits
- **`skill-improvement-trigger`** — After a meaningful task — trigger post-task learning capture if pipelines.skill_improvement is enabled
- **`skill-quality`** — Creating/editing/reviewing skills — minimum quality standard; every skill executable, validated, self-contained
- **`slash-command-routing-policy`** — User types a slash command like /create-pr, /commit, or pastes command file content
- **`source-of-truth`** — Editing files in dist/agent-src/, .augment/, .claude/, or .cursor/ — source of truth is src/; never edit a generated projection directly
- **`telegraph-speak`** — When telegraph.speak_scope != off — condense prose to telegraph grammar with carve-outs for numbered options, Iron-Law, code, paths, error markers
- **`token-efficiency`** — Running CLI tools, fetching logs, or producing replies — redirect verbose output, minimize tool calls, keep replies concise
- **`token-optimizer-maintenance`** — Editing a token-optimizer-cited asset (cli-output-handling, rtk-output-filtering, token-efficiency, markitdown) — sync catalog same commit
- **`tool-safety`** — Skill uses external tools — enforce allowlist, deny-by-default, no hidden credential patterns
- **`ui-audit-gate`** — Writing/editing UI — components, screens, layouts, design tokens — require existing-ui-audit findings first
- **`upstream-proposal`** — After creating or improving a skill/rule/guideline/command — ask if it should be contributed upstream to the shared package
- **`user-interaction`** — Asking a question, presenting options, summarizing progress — numbered-options Iron Law, single-recommendation rule, progress indicators
- **`user-interrupt-priority`** — User interrupts override the current task — STOP, complete new task in full, then ASK before resuming; never silently return to prior work

## Skills (58)

- **`adr-create`** — Use when capturing an architectural decision — naming the file, picking the next ADR number, filling Status / Context / Decision / Consequences, and regenerating the index — even without saying 'ADR'.
- **`agent-docs-writing`** — Use when reading, creating, or updating agent documentation, module docs, roadmaps, or AGENTS.md. Understands the full .augment/, agents/, and copilot-instructions structure.
- **`agents-md-thin-root`** — Use when editing AGENTS.md (package root) or templates/AGENTS.md (consumer) — enforces Thin-Root contract: hard char ceilings, ≥40% pointer ratio, mandatory emergency-triage block.
- **`ai-council`** — Use when polling external AIs (OpenAI, Anthropic) outside the host session for a neutral second opinion on a roadmap, diff, prompt, or file set — or 'cross-check with another model'.
- **`analysis-autonomous-mode`** — ONLY when user explicitly requests autonomous analysis, deep investigation, multi-step research, or 'dig into this end-to-end without asking me each step' — NOT for normal feature work.
- **`analysis-skill-router`** — Use when picking which analysis or project-analysis-* skill fits a request — routes by scope, framework, and symptom — even if the user just says 'analyze this' or 'dig into the codebase'.
- **`check-refs`** — Use when verifying cross-references between skills, rules, commands, guidelines, and context documents are not broken after edits, renames, or deletions.
- **`command-routing`** — Use when the user invokes a slash command like /create-pr, /commit, /fix-ci, or pastes command file content — routes to the right command with context inference and GitHub API patterns.
- **`command-writing`** — Use when creating or editing a slash command in src/agent-src/commands/ — frontmatter, numbered steps, safety gates — even when the user just says 'add a /command for X'.
- **`condense-memory`** — Use when shrinking always-loaded memory files (AGENTS.md, CLAUDE.md, .cursorrules) via telegraph grammar — refuses sensitive paths, round-trips via .original.md backup.
- **`context-authoring`** — Use when filling in knowledge-layer context files — auth-model, tenant-boundaries, data-sensitivity, deployment-order, observability — interactive walkthrough that turns templates into reviewer fuel.
- **`context-document`** — Use when the user says "create context", "document this area", or wants a structured snapshot of a codebase area for agent orientation.
- **`copilot-agents-optimization`** — Use when optimizing AGENTS.md or copilot-instructions.md — deduplicates against .augment/ content, enforces line budgets, and focuses each file on its audience.
- **`copilot-config`** — Tune the GitHub Copilot AI — `copilot-instructions.md`, PR-review patterns, suggestion behavior, output verbosity. NOT for dev-environment setup (use `devcontainer`).
- **`decision-record`** — Use when locking a trade-off, structuring an ADR draft, or wiring supersession chains — frames options · trade-offs · consequences before the file is written by `adr-create`.
- **`description-assist`** — Use when polishing a skill/rule/command/guideline frontmatter description — pushier phrasing, trigger coverage, undertrigger audit — even if the user just says 'make this pushier'.
- **`doc-coauthoring`** — Use when co-authoring a PRD, design doc, RFC, decision doc, or technical spec — 3-stage flow (context → section-by-section → reader-test) — even if the user just says 'help me write this spec'.
- **`file-editor`** — Use when opening edited files in the user's IDE. Reads settings from .agent-settings.yml to determine IDE and whether auto-open is enabled.
- **`guideline-writing`** — Use when creating or editing a guideline in docs/guidelines/ — reference material cited by skills, no auto-triggers — even when the user just says 'write up our naming conventions'.
- **`jira-integration`** — Use when the user says "check Jira", "create ticket", "update issue", or needs JQL queries, ticket transitions, or branch-to-ticket linking.
- **`judge-bug-hunter`** — Use when a diff needs correctness review — null-safety, edge cases, off-by-one, races, error handling — dispatched by /review-changes, /do-and-judge, /judge, even without 'judge'.
- **`judge-code-quality`** — Use when a diff needs a readability review — naming, single-responsibility, DRY, dead code, mismatch with codebase conventions — dispatched by /review-changes, /do-and-judge, /judge.
- **`judge-security-auditor`** — Use when a diff may introduce security risk — authZ, injection, secrets, unsafe deserialization, SSRF, XSS, mass assignment — dispatched by /review-changes, /do-and-judge, /judge.
- **`judge-test-coverage`** — Use when a diff may lack tests — missing assertions, uncovered branches, over-mocking, no regression test for a bug fix — dispatched by /review-changes, /do-and-judge, /judge, even without 'tests'.
- **`learning-to-rule-or-skill`** — Use when a repeated learning, mistake, or successful pattern should be turned into a new rule or skill. Also use after completing a task to capture learnings from the work.
- **`lint-skills`** — Use when running the package's skill linter against all skills and rules to validate frontmatter, required sections, and execution metadata.
- **`markitdown`** — Use when converting PDF, DOCX, XLSX, PPTX, EPUB, images, or audio to Markdown for LLM ingestion via the upstream markitdown-mcp server — 'extract this PDF', 'OCR this image', 'transcribe this audio'.
- **`mcp`** — Use when working with MCP (Model Context Protocol) servers — their tools, capabilities, and best practices for effective agent workflows.
- **`mcp-builder`** — Use when building an MCP server in Python (FastMCP) or Node/TypeScript (MCP SDK) — agent-centric tool design, input schemas, error handling, and the 10-question evaluation harness.
- **`md-language-check`** — Use BEFORE saving any .md under .augment/, dist/agent-src*/, or agents/ — scans umlauts, German function words, and German phrases outside DE:/EN: anchor blocks. Hard gate per language-and-tone.
- **`memory-consolidation`** — Use when consolidating session signals into curated memory — four-phase loop ORIENT → GATHER → CONSOLIDATE → PRUNE. Triggers on 'mine my sessions', 'consolidate memory', 'review intake signals'.
- **`module-detect-on-the-fly`** — Use when editing a file under a module-shaped path (`Modules/*`, `packages/*`, `apps/*`, `internal/*`) while `modules.enabled` is `false` — asks the user once whether to enable the config.
- **`module-management`** — Use when working within any module under `modules.root_paths` from `.agent-project-settings.yml` — Laravel HMVC, Symfony DDD-lite, Node monorepo, Python src/, Go internal/, or a custom path.
- **`override-management`** — Creates and manages project-level overrides for shared skills, rules, and commands — extending or replacing originals from .augment/ with project-specific behavior in agents/overrides/.
- **`persona-writing`** — Use when creating or editing a persona in src/agent-src/personas/ — voice / focus / unique questions / output expectations — even when the user just says 'add a reviewer voice for X'.
- **`project-docs`** — Use when looking for project-specific documentation. Knows which docs exist in agents/reference/docs/ and agents/settings/contexts/ and maps work areas to relevant docs.
- **`prompt-engineering-patterns`** — Use when designing production-LLM prompts — few-shot, chain-of-thought, system prompts, templates, self-verification — distinct from prompt-optimizer and refine-prompt.
- **`prompt-optimizer`** — Use when the user wants a prompt optimized for ChatGPT, Claude, Gemini, or another AI — 'make this prompt better', 'optimize for ChatGPT', 'rewrite my prompt' — even without saying 'optimize'.
- **`readme-reviewer`** — Use when reviewing a README for accuracy, usability, and alignment with the actual repository. Detects invented content, broken setup steps, and structural issues.
- **`readme-writing`** — Use when creating, rewriting, or significantly improving a README based on the actual repository structure, commands, and intended audience.
- **`readme-writing-package`** — Use when creating or rewriting a README for a reusable package or library. Focus on installability, minimal usage example, compatibility, and developer onboarding.
- **`refine-prompt`** — Reconstruct a free-form prompt into actionable AC + assumptions + confidence band before the engine plans — '/work "…"', 'baue X', 'ist der Prompt klar genug für die Engine?'.
- **`repomix-packer`** — Use when packaging a codebase to a single AI-friendly file for LLM analysis — local or remote, XML/Markdown/JSON, token counting, gitignore filtering, peer-side `repomix` CLI.
- **`review-routing`** — Use when preparing a PR description, suggesting reviewers, or flagging risk — produces owner-mapped roles plus historical bug-pattern matches from project-local YAML.
- **`roadmap-management`** — Use when the user says "create roadmap", "show roadmap", or "execute roadmap". Creates, reads, and manages roadmap files with phase tracking.
- **`roadmap-writing`** — Use when authoring or rewriting a roadmap in agents/roadmaps/ — phase prose, goal sentence, acceptance criteria, council notes — even when the user just says 'write a plan for X' or 'draft a roadmap'.
- **`rtk-output-filtering`** — Use when running verbose CLI commands — wraps them with rtk (Rust Token Killer) for 60-90% token savings. Covers installation, configuration, and usage patterns.
- **`rule-refactor`** — Use when the rule set is over the Augment budget, when a new rule would breach it, or when asked to audit / merge / prune rules — runs the audit pipeline and proposes a verdict per rule.
- **`rule-writing`** — Use when creating or editing a rule in src/rules/ — trigger wording, always vs auto classification, size budget — even when the user just says 'add a rule for X'.
- **`script-writing`** — Use when adding or editing any script under `scripts/` — `--quiet` flag, `_lib/script_output` helpers, silent Taskfile wiring, Iron-Law carve-outs — even when you just say 'add a check script for X'.
- **`sequential-thinking`** — ONLY when user explicitly requests: step-by-step reasoning, structured problem decomposition, or iterative analysis. NOT for regular coding tasks.
- **`skill-improvement-pipeline`** — ONLY when user explicitly requests: run the skill improvement pipeline after a learning was detected. Orchestrates capture, classify, create, validate, and apply.
- **`skill-management`** — Use when condensing, decondenseing, refactoring, or improving existing skills. Covers the full skill lifecycle from verbose → sharp → maintained.
- **`skill-reviewer`** — Use when reviewing, auditing, or optimizing skills — validates against the 7 Skill Killers checklist and produces fix recommendations.
- **`skill-writing`** — Use when deciding 'should this be a skill or a rule?', creating/improving/reviewing agent skills, SKILL.md frontmatter, or procedure sections — even without saying 'skill-writing'.
- **`subagent-orchestration`** — Use when orchestrating implementer/judge subagents — seven modes (do-and-judge ±two-stage, do-in-steps/parallel/worktrees, do-competitively, judge-with-debate) — models from .agent-settings.yml.
- **`token-optimizer`** — Use BEFORE any verbose CLI run, large file read, doc conversion, or near-context handoff — single decision tree keyed by intent that cites the canonical token-saving asset. Consult before the action.
- **`upstream-contribute`** — Use when a learning, new skill, rule improvement, or bug fix from a consumer project should be contributed back to the shared agent-config package.

## Templatess (1)

- **`proposal.example`** — _(no description)_
