@event4u/agent-config 2.10.0 → 2.12.0

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

@@ -3,6 +3,7 @@ name: agents
 tier: 1
 description: Agent-layer orchestrator — routes to init, optimize, audit. Covers AGENTS.md and its multi-tool stubs (CLAUDE.md, GEMINI.md, copilot-instructions.md, .cursorrules).
 cluster: agents
+type: orchestrator
 disable-model-invocation: true
 suggestion:
   eligible: true

package/.agent-src/commands/challenge-me.md

@@ -3,6 +3,7 @@ name: challenge-me
 tier: 2
 description: Challenge-me orchestrator — routes to vision, with-docs
 cluster: challenge-me
+type: orchestrator
 disable-model-invocation: true
 suggestion:
   eligible: true

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

@@ -3,6 +3,7 @@ name: chat-history
 tier: 2
 description: Chat-history orchestrator — routes to show, import, learn
 cluster: chat-history
+type: orchestrator
 disable-model-invocation: true
 suggestion:
   eligible: true

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

@@ -3,6 +3,7 @@ name: context
 tier: 2
 description: Context orchestrator — routes to create, refactor
 cluster: context
+type: orchestrator
 disable-model-invocation: true
 suggestion:
   eligible: true

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

@@ -3,6 +3,7 @@ name: council
 tier: 1
 description: Council orchestrator — routes to default, pr, design, optimize
 cluster: council
+type: orchestrator
 disable-model-invocation: true
 suggestion:
   eligible: true

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

@@ -3,6 +3,7 @@ name: feature
 tier: 1
 description: Feature orchestrator — routes to explore, plan, refactor, roadmap, dev
 cluster: feature
+type: orchestrator
 disable-model-invocation: true
 suggestion:
   eligible: true

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

@@ -3,6 +3,7 @@ name: fix
 tier: 1
 description: Fix orchestrator — routes to ci, references, portability, seeder, pr-comments, pr-bot-comments, pr-developer-comments
 cluster: fix
+type: orchestrator
 disable-model-invocation: true
 suggestion:
   eligible: true

package/.agent-src/commands/grill-me.md

@@ -3,6 +3,7 @@ name: grill-me
 tier: 2
 description: Alias for /challenge-me — interactive grill-style interview that sharpens a fuzzy plan/idea into a copyable Markdown pitch
 cluster: challenge-me
+type: orchestrator
 disable-model-invocation: true
 suggestion:
   eligible: true

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

@@ -3,6 +3,7 @@ name: judge
 tier: 1
 description: Judge orchestrator — routes to solo, steps, on-diff
 cluster: judge
+type: orchestrator
 disable-model-invocation: true
 suggestion:
   eligible: true

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

@@ -3,6 +3,7 @@ name: memory
 tier: 1
 description: Memory orchestrator — routes to add, load, mine-session, promote, propose
 cluster: memory
+type: orchestrator
 disable-model-invocation: true
 suggestion:
   eligible: true

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

@@ -3,6 +3,7 @@ name: module
 tier: 2
 description: Module orchestrator — routes to create, explore
 cluster: module
+type: orchestrator
 disable-model-invocation: true
 suggestion:
   eligible: true

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

@@ -153,11 +153,12 @@ rtk post-install steps (telemetry off, init --global) per
 ### 7. Confirm `cost_profile` and learning loop
 
 Read current `cost_profile` and `pipelines.skill_improvement` values.
-Present plainly (sensible defaults from template — `minimal` +
-`skill_improvement: true`):
+Present plainly (sensible defaults from template — `balanced` +
+`skill_improvement: true`; rationale in
+[`docs/contracts/cost-profile-defaults.md`](../docs/contracts/cost-profile-defaults.md)):
 
 ```
-> Cost profile: {current} (minimal by default — includes the learning loop)
+> Cost profile: {current} (balanced by default — kernel + tier-1 auto-rules)
 > Learning loop (skill_improvement): {current} (true by default)
 >
 > 1. Keep defaults — recommended
@@ -236,7 +237,34 @@ directly — the agent follows the merge rules in `layered-settings` when
 you ask it to change a value.
 ```
 
-### 11. Maintainer-only feature pointer
+### 11. Quickstart pointer — next command after onboarding
+
+Print next-action block so developer does **not** have to re-find README
+to start work. One screen, no question, no prompt:
+
+```
+🚀  Next step — your first real task
+
+  Try one of these from the same chat:
+
+    /work "your first real task"
+        Free-form prompt — agent refines, plans, implements, tests,
+        verifies, reports. A decision_result entry lands in agents/state/
+        confirming the work-engine ran end-to-end.
+
+    /implement-ticket PROJ-123
+        Ticket-driven flow — pulls Jira/Linear context, runs same
+        refine → memory → analyze → plan → implement → test → verify
+        → report sequence, halts on ambiguity.
+
+  Both honour decision_engine gates in .agent-settings.yml
+  (see docs/contracts/decision-engine-gates.md for schema).
+```
+
+Skip block in cloud surfaces (cloud agent's invocation surface is
+already chat window).
+
+### 12. Maintainer-only feature pointer
 
 Print one-screen hint after summary — no question, no prompt, just pointer
 for maintainers who want to opt into artefact-engagement telemetry layer.

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

@@ -3,6 +3,7 @@ name: optimize
 tier: 1
 description: Optimize orchestrator — routes to skills, agents-dir, augmentignore, rtk-filters
 cluster: optimize
+type: orchestrator
 disable-model-invocation: true
 suggestion:
   eligible: true

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

@@ -3,6 +3,7 @@ name: override
 tier: 2
 description: Override orchestrator — routes to create, manage
 cluster: override
+type: orchestrator
 disable-model-invocation: true
 suggestion:
   eligible: true

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

@@ -3,6 +3,7 @@ name: roadmap
 tier: 1
 description: Roadmap orchestrator — routes to create (authoring) and process-step / process-phase / process-full (autonomous execution).
 cluster: roadmap
+type: orchestrator
 disable-model-invocation: true
 suggestion:
   eligible: true

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

@@ -3,6 +3,7 @@ name: tests
 tier: 2
 description: Tests orchestrator — routes to create, execute
 cluster: tests
+type: orchestrator
 disable-model-invocation: true
 suggestion:
   eligible: true

package/.agent-src/skills/canvas-design/SKILL.md

@@ -0,0 +1,132 @@
+---
+name: canvas-design
+description: "Use when creating static visual art — posters, marketing visuals, brand assets, PDF/PNG design pieces — even if the user just says 'design a poster' or 'mach uns ein Visual'."
+source: package
+domain: product
+---
+
+# canvas-design
+
+## When to use
+
+Use when:
+
+* User asks for a poster, marketing visual, brand asset, social-media graphic, cover art
+* Output is a static `.pdf` or `.png` design piece (not a UI mockup, not a wireframe)
+* The deliverable is the visual artifact itself
+
+Do NOT use when:
+
+* Designing a UI component or app screen → `fe-design`, `ui-component-architect`, `react-shadcn-ui`, `blade-ui`, `flux`
+* Tailwind / shadcn / Flux component styling → `tailwind-engineer`
+* Brand voice / tone definition → `voice-and-tone-design`
+* Release announcement copy → `release-comms`
+
+## Goal
+
+Produce one finished visual artifact (`.pdf` or `.png`) backed by an original design philosophy. Both files ship together.
+
+The work emphasizes: visual expression over text · original direction (no artist mimicry) · composition that looks deliberated, not generated.
+
+## Preconditions
+
+* Brief from user (theme, intent, occasion, target medium, size constraint)
+* Output directory: `agents/design-assets/{slug}/` — create if missing
+* Image-generation tooling available (Python with Pillow / matplotlib / cairo, SVG → PNG conversion, or whatever the environment ships)
+
+## Procedure
+
+### 1. Brief intake
+
+One numbered-options block surfaces: theme / occasion · target medium + dimensions (web 1200×630? print A3? square 1080×1080?) · color & mood direction · hard constraints (logo required? color to avoid?) · single page or series.
+
+If the brief says "in the style of [living artist]", flag the copyright risk and propose an original direction.
+
+### 2. Design philosophy
+
+Author `agents/design-assets/{slug}/philosophy.md` — 4–6 paragraphs naming:
+
+* **Movement name** — 1–2 words ("Chromatic Silence", "Brutalist Joy", "Analog Meditation")
+* **Visual language** — how the philosophy manifests through space, form, color, scale, composition, rhythm
+* **Text role** — sparse, accent only; never paragraphs
+* **Craftsmanship anchor** — visible deliberation, not template polish
+
+Stay aesthetically specific but leave interpretive room for the canvas execution.
+
+### 3. Subtle conceptual thread
+
+Identify a single niche reference embedded in the work — not announced, woven into form / color / composition. A jazz musician quoting another song: those who know catch it, others enjoy the music.
+
+Document it in `philosophy.md` under `## Subtle reference`.
+
+### 4. Canvas execution
+
+Produce `agents/design-assets/{slug}/{slug}.{pdf|png}`:
+
+1. Pick the execution tool (Pillow, matplotlib, SVG, or framework-native)
+2. Limited palette — 2–5 colors, intentional and cohesive
+3. Geometric or organic forms per philosophy
+4. Text — sparse, design-forward, integrated as visual element; never overlapping, never falling off canvas
+5. Margins — every element contained, breathing room
+6. Repeating patterns, layered elements, systematic markers as the philosophy permits
+
+### 5. Refinement pass
+
+After the first render, **do not add more graphics**. Refine what exists:
+
+* Tighten composition cohesion
+* Adjust spacing, alignment, color balance
+* Replace fonts if they fight the philosophy
+* Remove any element that doesn't earn its place
+
+Render the refined version. Overwrite the artifact.
+
+### 6. Multi-page (optional)
+
+If the user requests a series, treat each page as a story beat — distinct but philosophically continuous. Bundle as a multi-page PDF or numbered PNGs (`{slug}-01.png`, `{slug}-02.png`, …).
+
+### 7. Validation
+
+* `philosophy.md` exists with movement name + 4–6 paragraphs + subtle-reference section
+* Artifact file exists at the expected path
+* Open and verify: nothing falls off canvas, no overlapping text, palette ≤ 5 distinct colors, every element has margin
+* Original work — no traceable artist-style copy
+
+## Output format
+
+1. `agents/design-assets/{slug}/philosophy.md`
+2. `agents/design-assets/{slug}/{slug}.{pdf|png}` (or numbered series for multi-page)
+3. One concluding line stating both file paths
+
+## Gotcha
+
+* **No artist mimicry** — copying a living artist's signature style is copyright risk and breaks the original-work mandate. Propose an original direction.
+* **Text discipline** — most pieces fail because text creeps in as paragraphs. Words are visual accents, not explanation.
+* **One canvas** — single page unless multi-page is explicitly requested.
+* **Font availability** — the environment may not ship your target font. Pick a fallback before render time, or download into the working dir first.
+* **Output location** — always `agents/design-assets/{slug}/`. Never write binary artifacts to the repo root or to source-of-truth dirs.
+* **Refinement loop is real** — first render is the draft, not the deliverable.
+
+## Frugality Standards
+
+Apply the [Frugality Charter](../../contexts/contracts/frugality-charter.md).
+
+* Per the default-terse rule, `philosophy.md` opens with the movement name — no "In this document I will describe …" frame.
+* Per the cheap-question check, numbered-options blocks only at brief intake (where consequences differ).
+* Per the post-action summary suppression, ship the files; skip an "## Artist statement" wrapper.
+
+**Pre-save self-check:**
+
+1. Does `philosophy.md` carry filler superlatives ("absolute pinnacle", "transcendent")?
+2. Does the canvas include explanatory text instead of visual-accent text?
+3. Are more than 5 distinct colors present without justification in the philosophy?
+4. Is the subtle reference announced explicitly in the visual, breaking the "those who know" principle?
+
+## Do NOT
+
+* Copy a living artist's signature visual style
+* Generate cartoony / amateur / template-store output
+* Add paragraphs of text — visuals communicate, words accent
+* Skip the philosophy file — the artifact without it is just an image
+* Skip the refinement pass
+* Write binary artifacts to the repo root or to source-of-truth dirs

package/.agent-src/skills/canvas-design/evals/triggers.json

@@ -0,0 +1,16 @@
+{
+  "skill": "canvas-design",
+  "description": "5 should-trigger + 5 should-not-trigger queries. Should-trigger asks for static visual art (poster / cover / marketing visual). Should-not-trigger near-misses share design vocabulary but route elsewhere (fe-design, tailwind-engineer, voice-and-tone-design, release-comms).",
+  "queries": [
+    {"q": "Need a launch poster for next week's release announcement — A3 print, minimal style", "trigger": true},
+    {"q": "Design us a social-media visual for the v3.0 release, 1080x1080 for IG", "trigger": true},
+    {"q": "Mach mir bitte ein Cover-Bild für den Talk nächste Woche, 1200x630 fürs Web", "trigger": true},
+    {"q": "We want a single-page PDF brand visual for the conference booth handout", "trigger": true},
+    {"q": "Build a minimalist poster for the team-offsite invitation, square format", "trigger": true},
+    {"q": "Design a new component library for our app — buttons, inputs, cards", "trigger": false},
+    {"q": "What color palette should we standardize on in tailwind.config.js?", "trigger": false},
+    {"q": "Refactor the brand voice doc — make it less corporate and more direct", "trigger": false},
+    {"q": "Draft the release announcement blog post for the v3.0 launch", "trigger": false},
+    {"q": "Help me wireframe the new onboarding flow — three screens, mobile-first", "trigger": false}
+  ]
+}

package/.agent-src/skills/doc-coauthoring/SKILL.md

@@ -0,0 +1,129 @@
+---
+name: doc-coauthoring
+description: "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'."
+source: package
+domain: process
+---
+
+# doc-coauthoring
+
+## When to use
+
+Use this skill when:
+
+* User starts a substantial writing task — PRD, RFC, design doc, decision doc, technical spec, proposal
+* User says "help me write this up", "draft a proposal", "we need a doc for X"
+* The output is a structured prose document the user will own and ship
+
+Do NOT use when:
+
+* Authoring agent docs / module docs / AGENTS.md → `agent-docs-writing`
+* Writing a README → `readme-writing` / `readme-writing-package`
+* Writing an ADR (process is fixed, no co-authoring loop) → `adr-create`
+* Code documentation, inline comments, docstrings
+
+## Goal
+
+Move from a fuzzy ask to a complete document the user owns, by:
+
+1. Closing the context gap before drafting
+2. Building each section through brainstorm → curate → draft → refine
+3. Testing the draft with a fresh-context reader before declaring done
+
+## Preconditions
+
+* User explicitly wants a document (not a quick answer)
+* `save-file` and `str-replace-editor` available
+* Target path and filename agreed up front
+
+## Procedure
+
+### 0. Inspect existing material
+
+Before any drafting, **inspect** the landscape: search `agents/` and
+the repo for related prior docs (`grep -ril "{topic}" agents/ docs/`),
+check the user's named ticket / thread for context, and confirm no
+in-flight document already covers the ask. If a near-duplicate exists,
+surface it and ask whether to extend or supersede.
+
+### 1. Context gathering
+
+Close the gap between what the user knows and what you know.
+
+1. **Meta-questions** — one numbered-options block (per `user-interaction`): doc type? primary audience? desired impact? template/format constraint? existing related docs / threads / tickets?
+2. **Info dump** — invite stream-of-consciousness context: plain text, paths to existing docs, ticket links, thread paste.
+3. **Clarifying questions** — 5–10 numbered questions to fill remaining gaps. User answers shorthand (`1: yes`, `2: see #channel`, `3: backwards-compat reason`).
+4. **Exit gate** — ask "ready to draft, or more context?" — wait for confirmation. Do not start scaffolding the file until the user confirms.
+
+### 2. Refinement & structure
+
+Build the document section by section.
+
+1. **Agree on structure** — propose 3–5 sections based on doc type and context. Ask user to confirm or adjust.
+2. **Scaffold the file** — use `save-file` to create the doc with placeholder text per section (`[To be written]`). One commit-equivalent action; review with the user before populating.
+3. **Pick the starting section** — suggest the one with the most unknowns (usually the core decision / proposal). Never start with the summary.
+4. **Per-section loop** — repeat for each section:
+   - **Clarifying questions** — 5–10 numbered questions about what this section covers
+   - **Brainstorm** — 5–20 numbered options of what could go in. Offer "more options?" at the end.
+   - **Curation** — user picks: `keep 1,4,7,9` / `remove 3 (dupes 1)` / `combine 11+12`. Parse freeform feedback if the user gives `"looks good but ..."`.
+   - **Gap check** — "anything missing for this section?"
+   - **Draft** — `str-replace-editor` to replace the placeholder. Never reprint the whole doc.
+   - **Iterate** — user feedback in, surgical edits out. After 3 iterations with no substantial change, ask "anything to remove without losing value?"
+   - **Section exit gate** — "section done — move to next?"
+5. **Whole-doc review at 80% complete** — re-read the full file. Surface contradictions, redundancy, generic filler. Apply final edits.
+
+### 3. Reader test
+
+Verify the doc works for someone without your context.
+
+1. **Predict reader questions** — generate 5–10 questions a real reader would ask after reading.
+2. **Run the test** — pick one:
+   - **`ai-council` available** → invoke with the doc + predicted questions; treat each council member as a fresh reader.
+   - **Otherwise** → instruct the user to open a fresh Claude / ChatGPT, paste the doc, ask the questions one by one. Capture answers.
+3. **Additional fresh-reader checks** (always): "what is ambiguous?" · "what context does this doc assume readers have?" · "internal contradictions?"
+4. **Report** — surface where the fresh reader got it wrong, where assumptions break.
+5. **Loop back to Stage 2** for problematic sections until the fresh reader answers cleanly and surfaces no new gaps.
+
+### 4. Handover
+
+1. Final read-through by the user (they own the doc).
+2. Verify facts, links, technical details.
+3. Confirm intended impact achieved.
+4. Surface the final file path. Done.
+
+## Output format
+
+1. Target document file at the agreed path (e.g. `agents/proposals/{slug}.md`)
+2. One concluding line stating "Doc complete at {path} — ready for owner review"
+
+## Gotcha
+
+* **One question per turn** (Iron Law from `ask-when-uncertain`) — never bundle clarifying + brainstorm + curate prompts in one message.
+* **Never reprint the full doc** during iteration — always use `str-replace-editor`. Reprinting wastes tokens and creates merge drift.
+* **Reader test is not optional** — without it, you ship the version that makes sense to you, not to readers. Skip only on explicit user override.
+* **Sub-agent absence** — `ai-council` may not be configured. Have the manual fresh-Claude fallback ready (Stage 3 step 2).
+* **Image alt-text** — if the doc embeds images, add alt-text inline; without it, fresh-reader tools can't see them.
+* **Language discipline** — keep the doc body in English (per `language-and-tone`). For verbatim German user phrases or interview quotes, use `DE: … · EN: …` anchor blocks.
+
+## Frugality Standards
+
+Apply the [Frugality Charter](../../contexts/contracts/frugality-charter.md).
+
+* Per the default-terse rule, each section opens with content, not "In this section …".
+* Per the cheap-question check, numbered-options blocks only when consequences differ — skip "yes / no, continue?" type prompts.
+* Per the post-action summary suppression, the final output is the doc — no wrapping "Summary of what we did" block.
+
+**Pre-save self-check:**
+
+1. Does any section open with a narrative preamble instead of content?
+2. Are clarifying questions bundled when one-at-a-time would surface user priorities better?
+3. Is the reader-test stage skipped or merged into a "we're done" claim?
+4. Is non-English prose present outside `DE: / EN:` anchor blocks?
+
+## Do NOT
+
+* Skip Stage 1 — straight-to-drafting produces docs that miss audience and impact
+* Bundle 5+ questions into one numbered block — breaks one-question-per-turn
+* Reprint the whole doc on every iteration
+* Declare "done" without the Stage 3 reader test
+* Generate doc content from scratch when the user has existing context — gap-closing is the whole point

package/.agent-src/skills/doc-coauthoring/evals/triggers.json

@@ -0,0 +1,16 @@
+{
+  "skill": "doc-coauthoring",
+  "description": "5 should-trigger + 5 should-not-trigger queries. Should-trigger phrasings reflect real co-authoring asks for PRDs / specs / decision docs. Should-not-trigger near-misses share doc-writing vocabulary but route elsewhere (agent-docs-writing, readme-writing, adr-create, code docs, translations).",
+  "queries": [
+    {"q": "Help me draft a PRD for the new analytics feature — I have a lot of context but no structure yet", "trigger": true},
+    {"q": "We need a design doc for the OAuth migration before next week's review. Can you walk me through writing it?", "trigger": true},
+    {"q": "I have to write up a decision doc about dropping Redis. Where do we start?", "trigger": true},
+    {"q": "Need an RFC for the data-export rate-limit change before tomorrow's architecture sync", "trigger": true},
+    {"q": "Lass uns einen Spec für das neue Webhook-Verfahren zusammenstellen — du fragst, ich antworte", "trigger": true},
+    {"q": "Add a section to AGENTS.md about the new env vars we just introduced", "trigger": false},
+    {"q": "Update the README with the new install instructions for the docker variant", "trigger": false},
+    {"q": "Write an ADR for the queue-broker switch from Redis to SQS", "trigger": false},
+    {"q": "Add docstrings to all public methods on the OrderService class", "trigger": false},
+    {"q": "Translate the lang/de strings to French for the new locale rollout", "trigger": false}
+  ]
+}