@event4u/agent-config 1.34.0 → 1.35.0

package/.agent-src/skills/release-comms/SKILL.md

@@ -0,0 +1,123 @@
+---
+name: release-comms
+description: "Use when turning a shipped changelog into a release narrative — value-not-feature framing, audience-segmented surfaces, one source of truth. Triggers on 'announce the release', 'write changelog post'."
+status: active
+tier: senior
+source: package
+domain: product
+context_spine: [product, team]
+---
+
+# release-comms
+
+## When to use
+
+- Release shipping with user-facing change, team about to send feature-list email.
+- Changelog draft reads like commit log — engineering-honest, unparseable for user.
+- Multiple comms surfaces (in-app, email, social, docs) about to be written by different people from same release.
+
+Do NOT use for incident comms (see `incident-commander`),
+deprecation announcements needing legal sign-off, or pre-release
+discovery — this skill assumes change is **shipped**.
+
+## Cognition cluster
+
+- **Mental model 16 — Leading vs. lagging indicators.** Release note
+  is lagging artifact; leading version = in-app prompt that fired
+  before user found change-log. See
+  [`docs/contracts/mental-models.md`](../../../docs/contracts/mental-models.md) § 16.
+- **Value-not-feature heuristic.** Every paragraph passes *"so the
+  user can ___"* completion. Failing rows go back for re-write.
+
+## Procedure
+
+### Step 0: Ground the release
+
+1. Read merged PR list / changelog block / release branch diff. Release = **what**; comms = **so what**. Conflate the two → ship marketing.
+2. Read **product** and **team** slots of [context-spine](../../../docs/contracts/context-spine.md) (if consumer filled them) for bounded scope and cadence — surface choice depends on cadence (weekly: in-app + log; quarterly: email + post; major: all four).
+3. Identify **single dominant change** the release ships. Three "headliners" reads as three half-announcements.
+
+### Step 1: Audience-segment
+
+1. Three audiences max: **active user**, **at-risk / lapsed user**, **prospect**. More fragments message; fewer hides routing.
+2. Per audience, write one sentence: *"After this release, you can …"* completing with user-side verb, not product-side feature.
+3. If two audiences end up with same sentence, collapse — segmentation that does not change message = theatre.
+
+### Step 2: Map surfaces to audiences
+
+1. **Changelog** (always) — engineers + power users; truthful, dense, link-heavy. Source of truth — every other surface points back here.
+2. **In-app prompt** — active users; ≤ 1 sentence + 1 CTA; fires for users whose past behaviour predicts they'll touch the new path.
+3. **Email** — at-risk / lapsed; one headline value, one CTA, one paragraph of context. No feature lists.
+4. **Social / blog** — prospect; the **why**, not the **what** — frame against user job (cite [`customer-research`](../customer-research/SKILL.md) if switch-event surfaced).
+
+Cut surfaces aggressively. Weekly release does not need blog post.
+
+### Step 3: Draft each surface from the changelog
+
+1. Open changelog. Per surface, copy dominant change line, then **rewrite verb subject** from "we" to "you".
+2. Strip qualifiers ("now", "even better", "lightning-fast"). Noise, not signal.
+3. Run *"so the user can ___"* completion on every paragraph. Failing paragraphs cut, not edited.
+
+### Step 4: Truth-check
+
+1. Every claim links back to changelog row or doc URL. Unsourced claim → cut.
+2. No tense games — past for shipped, future for coming-soon (and only if date is committed). "Roadmap" lives outside this skill.
+3. Names match product surface. In-app says "Reports" and email says "Insights" → user fires lookup tax.
+
+### Step 5: Hand off
+
+1. Produce four artifacts (see `## Output`).
+2. Hand to whoever owns send. Do not embed scheduling or A/B test plans here — that is RevOps.
+
+## Related Skills
+
+**WHEN to use this**
+
+- Change is **shipped** and needs to reach existing users.
+- Multiple comms surfaces written by different people from same source.
+- Team about to default to feature-list email.
+
+**WHEN NOT to use this**
+
+- Production incident comms → [`incident-commander`](../incident-commander/SKILL.md).
+- Pre-release discovery / validation → [`customer-research`](../customer-research/SKILL.md).
+- Funnel-stage diagnostics post-release → [`funnel-analysis`](../funnel-analysis/SKILL.md).
+- Ranking which release to comms next → [`rice-prioritization`](../rice-prioritization/SKILL.md).
+
+## When the agent should load this
+
+- "Write the release notes for sprint 47."
+- "We're shipping the new export — how do we announce it?"
+- "Draft the changelog email for last week's batch."
+- "What's the in-app prompt copy for the redesign?"
+- "Turn the merged PR list into something users can read."
+
+## Output
+
+1. **`release-narrative.md`** — single source of truth: dominant change, audiences (1–3), per-audience *"After this release, you can …"* sentence, links to source changelog rows.
+2. **`changelog-entry.md`** — engineer-honest, dense, link-heavy block ready to paste into project's changelog.
+3. **`comms-pack.md`** — per-surface drafts (in-app prompt, email, optional social/blog), each ≤ surface's hard cap, each pointing back to `changelog-entry.md`.
+4. **`comms-checklist.md`** — pre-send checks: every claim sourced, names consistent across surfaces, audience match, "so the user can …" completion passing on every paragraph. Hand-off artifact for senior PO ([`product-owner`](../../personas/product-owner.md)).
+
+## Gotcha
+
+- Default failure mode = feature-list email — written to make engineering feel seen, not to help user.
+- Marketing puffery ("revolutionary", "delightful") fails source check; cut on sight.
+- Two surfaces using different names for same thing = highest-frequency support-ticket trigger after release.
+- Hidden coming-soon claims in past-tense paragraphs erode trust faster than missing the comms entirely.
+
+## Do NOT
+
+- Do NOT promote coming-soon item alongside shipped items — user cannot tell which is which and stops trusting next note.
+- Do NOT let long-tail change steal the headline — dominant change earns headline, long tail goes in changelog.
+- Do NOT ship surfaces without truth-check pass; unsourced claim survives in social longer than release does.
+
+## Runnable example
+
+Sprint 47 ships a one-click monthly export and three small bug fixes:
+
+- Dominant change: one-click export. Bug fixes go in changelog only.
+- Audiences: active user (will use it), at-risk (export friction was churn trigger per [`customer-research`](../customer-research/SKILL.md) evidence-log).
+- "After this release, you can pull a board-ready monthly report in one click." (active, at-risk — same sentence ⇒ collapse to one).
+- Surfaces: changelog (full), in-app prompt to active users on next month-end, email to at-risk cohort with same sentence and one CTA. No social.
+- Truth-check: claim links to export PR; "one click" is literal — verified against shipped UI.

package/.agent-src/skills/roadmap-writing/SKILL.md

@@ -162,6 +162,6 @@ to every roadmap you author.
 
 ## Examples
 
-Browse `agents/roadmaps/` (active plate) and `agents/roadmaps/archive/`
+Browse `agents/roadmaps/` (active set) and `agents/roadmaps/archive/`
 (closed work) for canonical structural / tactical / structural-with-council
 examples.

package/.agent-src/skills/stakeholder-tradeoff/SKILL.md

@@ -1,12 +1,15 @@
 ---
 name: stakeholder-tradeoff
 description: "Use when stakeholders pull a decision in different directions — frames each lens, builds a trade-off matrix, surfaces the cost of every choice — even if the user just says 'PO and ops disagree'."
+status: active
+tier: senior
+source: package
+domain: product
+context_spine: [team, product]
 personas:
   - product-owner
   - stakeholder
   - critical-challenger
-source: package
-domain: product
 ---
 
 # stakeholder-tradeoff
@@ -38,6 +41,26 @@ Do NOT use when:
 - The trade-off is risk-only — route to
   [`risk-officer`](../risk-officer/SKILL.md).
 
+## Cognition cluster
+
+- **Mental model 5 — Opportunity cost.** Every `+` on the matrix is
+  also an opportunity cost on the stakeholders not getting that
+  benefit; the matrix only earns its keep when it surfaces who pays
+  for the chosen `+`. See
+  [`docs/contracts/mental-models.md`](../../../docs/contracts/mental-models.md) § 5.
+- **Mental model 27 — Outcome over output.** Picking the option with
+  the most checkmarks is output theatre; pick the option whose `–`
+  cells land on stakeholders who can execute mitigations. See
+  `mental-models.md` § 27.
+- **Mental model 29 — Pre-mortems.** For the recommended option,
+  state the failure mode each `–`-bearing stakeholder will name in
+  six months. If you cannot, the lens is incomplete — re-interview.
+  See `mental-models.md` § 29.
+- **Team + product context-spine slots.** Read **team** for the
+  silent-stakeholders inventory (on-call, support, finance) and
+  **product** for end-user / segment lenses (free vs paid, region,
+  cohort). See [`context-spine`](../../../docs/contracts/context-spine.md).
+
 ## Procedure
 
 ### 1. Identify the stakeholders
@@ -98,7 +121,40 @@ everywhere, the trade-off paragraph names a concrete cost (not just
 cells the named owner can execute. Ensure no silent stakeholder
 column is missing.
 
-## Output format
+## Related Skills
+
+**WHEN to use this**
+
+- A request crosses two stakeholder lenses (eng ↔ PO, PO ↔ ops, ops
+  ↔ infra) and the trade-off is **not yet code**.
+- The room agrees on the goal but disagrees on who absorbs the cost.
+- A roadmap step has *un*declared trade-offs that need surfacing
+  before commit.
+
+**WHEN NOT to use this**
+
+- The conflict surfaces **inside an open PR** (test-coverage fails
+  but PO wants to ship) — start with `code-review-multi-lens`
+  (sibling C8); a C8 verdict that surfaces stakeholder conflict
+  becomes input to this skill for escalation. Boundary prose lives
+  in [`docs/guidelines/cross-role-handoff.md`](../../../docs/guidelines/cross-role-handoff.md).
+- The trade-off is purely technical (perf vs storage, sync vs async)
+  — route to [`decision-record`](../decision-record/SKILL.md).
+- The dominant axis is risk, not stakeholder cost — route to
+  [`risk-officer`](../risk-officer/SKILL.md).
+- The output is the locked decision artifact — hand off to
+  [`decision-record`](../decision-record/SKILL.md) once the matrix
+  is built.
+
+## When the agent should load this
+
+- "Wer zahlt was bei dieser Entscheidung?"
+- "PO und Ops sind sich uneinig — wir brauchen Klarheit."
+- "Was ist der Trade-off zwischen X und Y für die einzelnen Lenses?"
+- "Stakeholder-Konflikt vor dem Commit auflösen."
+- "Diese Roadmap-Phase hat undeclared trade-offs."
+
+## Output
 
 The trade-off report is a single block with these ordered fields:
 
@@ -147,3 +203,35 @@ Next:           /decision-record  to lock the choice
   if it exists, the trade-off was imaginary; surface that.
 - Do NOT lock the choice in this skill; hand off to
   `decision-record`.
+
+## Runnable example
+
+A pricing-page rewrite that ships faster vs gives ops more lead time:
+
+- Decision: *"Should the pricing-page rewrite ship in 2 weeks
+  (option A) or 4 weeks with a managed rollout (option B)?"*
+- Stakeholders:
+  - **PO** wants: revenue lift on Q-end · fears: churn signal in
+    the noise · trades: copy polish for time-to-ship.
+  - **On-call eng** wants: change window outside Friday · fears:
+    Saturday paging on a marketing rollout · trades: shippable A/B
+    framework for a deploy gate.
+  - **Support lead** wants: scripted answers for the new tier ·
+    fears: ticket-volume spike unprepared · trades: depth of
+    answers for breadth.
+  - **End-user (free tier)** wants: clear "what stays free" line ·
+    fears: silent paywall on a feature they rely on · trades:
+    nothing — silent stakeholder.
+- Matrix splits hardest on **operational load** (option A: `–` for
+  on-call + support, `+` for PO) and **clarity for end-users**
+  (option B: `+` for support + end-user, `–` for PO timing).
+- Trade-off in plain language: *"Option A means PO hits Q-end, but
+  on-call carries a marketing-rollout pager and support eats ticket
+  spikes blind. Option B means support and end-users land softly,
+  but PO slips two weeks past Q-end."*
+- Recommendation: option B. Rationale: the `–` cells in option A
+  land on stakeholders who **cannot** mitigate from inside the
+  rollout (free-tier user has no voice in the room).
+- Next: `/decision-record` to lock option B; the supersession chain
+  cites the original "ship by Q-end" mandate as the constraint that
+  changed.

package/.agent-src/skills/voc-extract/SKILL.md

@@ -0,0 +1,164 @@
+---
+name: voc-extract
+description: "Use when extracting Voice-of-Customer themes from existing artefacts — GH issues, PR threads, Sentry patterns. Triggers on 'what are users saying', 'recurring complaints', 'top themes'."
+status: active
+tier: senior
+source: package
+domain: product
+context_spine: [product]
+---
+
+# voc-extract
+
+## When to use
+
+- A backlog or planning round needs grounded user-voice signal, not anecdotes.
+- A round of bug reports / feature requests / Sentry events has accumulated and the team needs themes with citation per theme.
+- A roadmap proposal needs a "what users keep telling us" backing section.
+
+Do NOT use this skill for live interviews
+([`discovery-interview`](../discovery-interview/SKILL.md)) or for
+quantitative funnel diagnosis ([`funnel-analysis`](../funnel-analysis/SKILL.md)).
+
+## Bounded scope
+
+- **Read-only on artefacts the host already has** — local repo issues
+  (`gh issue list`), PR discussions (`gh pr view`), Sentry projects
+  the team owns. No external scrape, no SaaS API calls.
+- **Chat-export sourcing (Discord, Slack) is deferred** pending
+  privacy review (council Q5, SHIP-WITHOUT). If a request asks for
+  chat-derived VoC, refuse and route the user to a privacy review.
+- **No PII surfacing** — quotes are paraphrased to remove names,
+  emails, tenant identifiers; verbatim is reserved for product-team
+  artefacts inside the repo.
+
+## Cognition cluster
+
+- **Mental model 15 — Signal vs noise.** A loud single reporter
+  swamps quiet recurring patterns; rank by **distinct authors**, not
+  comment count. See
+  [`docs/contracts/mental-models.md`](../../../docs/contracts/mental-models.md) § 15.
+- **Mental model 14 — Pareto.** Roughly 20% of themes carry 80% of
+  the contact volume; cut the long tail explicitly so the team acts
+  on the head. See `mental-models.md` § 14.
+- **Mental model 22 — Data-informed, not data-driven.** Issue counts
+  are evidence, not voting; weight by recency, severity, and segment
+  before recommending. See `mental-models.md` § 22.
+- **Product context-spine slot.** Read **product** for segments,
+  non-goals, and focal jobs; do not surface themes that fall outside
+  the declared scope without a scope-violation flag. See
+  [`context-spine`](../../../docs/contracts/context-spine.md).
+
+## Procedure
+
+### 1. Inventory the source artefacts
+
+Identify what is in scope **for this run**:
+
+- `gh issue list --state all --limit N` per repo.
+- `gh pr list --state all --limit N` per repo.
+- Sentry project names + date window.
+
+Capture counts and date window in the output header so the verdict
+is reproducible.
+
+### 2. Inspect each artefact and tag
+
+Per artefact, capture:
+
+- **Theme tag** (free-text, normalised in step 3).
+- **Author** (distinct identity).
+- **Severity** — blocking / friction / wish / praise.
+- **Segment** — derived from the **product** spine slot.
+- **Citation** — `repo#123`, PR URL, Sentry issue ID.
+
+### 3. Normalise and rank
+
+Cluster theme tags into 5–12 themes max. For each:
+
+- **Distinct-author count** (the rank key).
+- **Severity mix** (blocking-share matters more than wish-share).
+- **Recency** — last 90 days vs older; weight 2× recent.
+- **Segment skew** — does the theme cluster in one segment?
+
+Drop themes with `< 3` distinct authors **unless** severity is
+blocking or the theme is brand-new in the recency window.
+
+### 4. Build the theme report and validate
+
+One row per theme. Columns: **theme · distinct authors · severity
+mix · recency · segment skew · representative citations (≤ 3) ·
+proposed next step (refine / probe / defer)**.
+
+Validate the report before handing back: verify each row cites
+≥ 1 artefact, check that distinct-author counts match the source
+inventory from step 1, confirm no PII leaked into the citations,
+and ensure no theme rated `defer` lacks a written rationale.
+
+### 5. Surface scope violations
+
+Themes that fall outside the **product** spine slot's declared scope
+go into a `scope-violation.md` block, never silently into the main
+report. The team decides whether to expand scope or close the door.
+
+### 6. Hand back
+
+Route refine candidates to [`refine-ticket`](../refine-ticket/SKILL.md);
+route probe candidates (need live interview) to
+[`discovery-interview`](../discovery-interview/SKILL.md); defer the
+rest with explicit rationale.
+
+## Related Skills
+
+**WHEN to use this**
+
+- The signal needs to come from existing repo / Sentry artefacts.
+- The output is a theme list with citation, not narrative summary.
+- A roadmap proposal needs grounded VoC backing.
+
+**WHEN NOT to use this**
+
+- The signal needs a live conversation — route to
+  [`discovery-interview`](../discovery-interview/SKILL.md).
+- The artefacts are chat-export sourced (Discord, Slack) — refuse
+  and route to a privacy review (deferred per bounded scope).
+- The output is a quantitative funnel — route to
+  [`funnel-analysis`](../funnel-analysis/SKILL.md).
+- A theme is already a ticket candidate — route directly to
+  [`refine-ticket`](../refine-ticket/SKILL.md).
+
+## When the agent should load this
+
+- "Was sagen die User wirklich?"
+- "Top-Themen aus den letzten 90 Tagen Issues."
+- "Welche Sentry-Patterns sind recurring?"
+- "Backe der Roadmap-Phase ein VoC-Block dazu."
+- "Gibt es ein Segment, das uns überproportional pingt?"
+
+## Output
+
+1. **Header** — sources scanned, counts, date window, scope notes.
+2. **Theme report table** — themes, distinct authors, severity mix,
+   recency, segment skew, citations, next step.
+3. **Scope-violation block** — themes outside the product spine
+   slot, explicit, never collapsed into the main table.
+4. **Routing list** — refine / probe / defer rows with the named
+   downstream skill per theme.
+
+## Gotcha
+
+- One articulate user can own three themes; rank by distinct authors
+  or you ship their backlog.
+- A theme with no recency (all > 90 days) is archaeology, not VoC;
+  flag it explicitly.
+- Chat-export requests are tempting (Discord copy-paste); refuse
+  per bounded scope until the privacy review lands.
+
+## Do NOT
+
+- Do NOT scrape external sources or hit SaaS APIs the team does not
+  already own.
+- Do NOT surface PII; paraphrase before quoting.
+- Do NOT collapse scope-violations into the main table.
+- Do NOT lock decisions inside this skill — hand off to
+  `refine-ticket` or `decision-record`.

package/.agent-src/templates/roadmaps.md

@@ -43,6 +43,15 @@ Templates for roadmap files stored in `agents/roadmaps/` or `app/Modules/{Module
     or budget-invariant changes; multi-round council, file-ownership
     matrices, > 600 lines. Enforced by `task lint-roadmap-complexity`.
     Standard: [`docs/contracts/roadmap-complexity-standard.md`](../docs/contracts/roadmap-complexity-standard.md).
+16. **No time-boxed plates, no visible-horizon sections.** Roadmaps describe
+    scope and phase ordering, not week-by-week commitments. No
+    `## Horizon (N-week visible plate)` sections, "Inside / outside the
+    plate" framings, `In-plate?` columns, or `**Out-of-plate.**` /
+    `**Out-of-horizon.**` / `(out-of-horizon, gated on Phase N)` suffixes.
+    AI execution does not operate on calendar plates; scope ordering and
+    dependency gates suffice. Pacing is the user's call, decided per turn
+    — never encoded into the plan. Enforced by `task lint-roadmap-complexity`
+    (plate-token detection).
 
 ---
 

package/.claude-plugin/marketplace.json

@@ -6,7 +6,7 @@
   },
   "metadata": {
     "description": "Shared agent configuration \u2014 skills for AI coding tools (Claude Code, Augment, Cursor, Cline, Windsurf, Gemini CLI).",
-    "version": "1.34.0"
+    "version": "1.35.0"
   },
   "plugins": [
     {
@@ -59,6 +59,7 @@
         "./.claude/skills/commit",
         "./.claude/skills/commit-in-chunks",
         "./.claude/skills/composer-packages",
+        "./.claude/skills/competitive-positioning",
         "./.claude/skills/compress",
         "./.claude/skills/context",
         "./.claude/skills/context-authoring",
@@ -76,6 +77,7 @@
         "./.claude/skills/council-pr",
         "./.claude/skills/create-pr",
         "./.claude/skills/create-pr-description-only",
+        "./.claude/skills/customer-research",
         "./.claude/skills/dashboard-design",
         "./.claude/skills/data-flow-mapper",
         "./.claude/skills/database",
@@ -88,6 +90,7 @@
         "./.claude/skills/design-review",
         "./.claude/skills/devcontainer",
         "./.claude/skills/developer-like-execution",
+        "./.claude/skills/discovery-interview",
         "./.claude/skills/docker",
         "./.claude/skills/dto-creator",
         "./.claude/skills/e2e-heal",
@@ -145,6 +148,7 @@
         "./.claude/skills/laravel-reverb",
         "./.claude/skills/laravel-scheduling",
         "./.claude/skills/laravel-validation",
+        "./.claude/skills/launch-readiness",
         "./.claude/skills/learning-to-rule-or-skill",
         "./.claude/skills/lint-skills",
         "./.claude/skills/livewire",
@@ -219,6 +223,7 @@
         "./.claude/skills/receiving-code-review",
         "./.claude/skills/refine-prompt",
         "./.claude/skills/refine-ticket",
+        "./.claude/skills/release-comms",
         "./.claude/skills/repomix-packer",
         "./.claude/skills/requesting-code-review",
         "./.claude/skills/research",
@@ -279,6 +284,7 @@
         "./.claude/skills/using-git-worktrees",
         "./.claude/skills/validate-feature-fit",
         "./.claude/skills/verify-completion-evidence",
+        "./.claude/skills/voc-extract",
         "./.claude/skills/websocket",
         "./.claude/skills/work"
       ]

package/CHANGELOG.md

@@ -318,6 +318,40 @@ our recommendation order, not its support status.
   users" tension without removing any path that an existing user
   might rely on.
 
+## [1.35.0](https://github.com/event4u-app/agent-config/compare/1.34.0...1.35.0) (2026-05-10)
+
+### Features
+
+* **personas:** add three Wave-2 specialist personas ([fafe78c](https://github.com/event4u-app/agent-config/commit/fafe78cd1d6ec4aa7edb9e6ebbe8bc61f661818d))
+* **skills:** add four senior product/strategy skills ([35e399d](https://github.com/event4u-app/agent-config/commit/35e399d4a805217d4e01a70b8795583eb11b046e))
+* **skills:** promote decision-record and stakeholder-tradeoff to tier:senior ([dec2369](https://github.com/event4u-app/agent-config/commit/dec2369ec8e273b29d701ba72c9283b47d545732))
+* **lint:** enforce context_spine slot citation in skill bodies ([2283472](https://github.com/event4u-app/agent-config/commit/22834723003ce515f6067ec228f273e13bf71cb2))
+* **lint:** detect plate/horizon convention in lint-roadmap-complexity ([8dcd6c1](https://github.com/event4u-app/agent-config/commit/8dcd6c1c4d9f772df2495e114a1b1a03c64022dc))
+* **personas:** upgrade product-owner to senior specialist ([e46fdad](https://github.com/event4u-app/agent-config/commit/e46fdadfd9645de6f07ee7516d265760f739ba73))
+* **skills:** add senior customer-research and release-comms ([fb17b8f](https://github.com/event4u-app/agent-config/commit/fb17b8f1641cd26ceeb405537711bacd1059317d))
+* **contracts:** add context-spine, mental-models, and cross-role-handoff ([a8bd106](https://github.com/event4u-app/agent-config/commit/a8bd106e77a092da385461aec508a8959179559d))
+
+### Bug Fixes
+
+* **skills:** cite team spine slot in customer-research ([9279606](https://github.com/event4u-app/agent-config/commit/9279606fedc60377306c80a14c6379577233ce3d))
+* **skill:** drop unused 'team' slot from customer-research context_spine ([e581c66](https://github.com/event4u-app/agent-config/commit/e581c664237f23c9804bce95fd0e8436d33d8bec))
+* **context-spine:** drop transient roadmap references ([a2e17c7](https://github.com/event4u-app/agent-config/commit/a2e17c7ef287b89a92aa296f8eb519ced78e3dcd))
+
+### Chores
+
+* **sync:** refresh compression hashes after main merge ([2689a99](https://github.com/event4u-app/agent-config/commit/2689a9959c0d8f5bb0b00a8b4cbc73485b81086d))
+* **generate-tools:** register new skills + personas in distribution layers ([1c8081d](https://github.com/event4u-app/agent-config/commit/1c8081d54b14214ac5163986784af1f4e505aa7d))
+* **roadmap:** archive road-to-unified-senior-roles, refresh dashboard ([0f7a203](https://github.com/event4u-app/agent-config/commit/0f7a203c9f3a6cb97837db52906fa7bd6ff9134a))
+* **sync:** refresh compression hash for customer-research ([5296bd1](https://github.com/event4u-app/agent-config/commit/5296bd13976e105ff128a90de05de78183745f67))
+* **sync:** refresh compression hashes after roadmap-plate removal ([75d06e1](https://github.com/event4u-app/agent-config/commit/75d06e1ec33d9472fd8ae4a08f5efd526b577905))
+* **roadmaps:** strip plate/horizon framing from 7 active roadmaps ([186f98e](https://github.com/event4u-app/agent-config/commit/186f98e8fa3405927e5543c41f4ce797b46eaedf))
+* **infra:** drop horizon-marker handling from process-loop and process-full ([9f9b968](https://github.com/event4u-app/agent-config/commit/9f9b9681f9b9d21305a69e3c413dc4b8ff7d5a9a))
+* **template:** forbid time-boxed plates in roadmap template (rule 16) ([12748c2](https://github.com/event4u-app/agent-config/commit/12748c2e3354e324b2d4b889ecda5655f3286738))
+* **ownership:** regenerate ownership matrix ([33d3775](https://github.com/event4u-app/agent-config/commit/33d37755e4af051df73cfae6b6c6ccc4981202e1))
+* **sync:** regenerate counts, hashes, and roadmap progress ([e4397f8](https://github.com/event4u-app/agent-config/commit/e4397f83bf5c5b10c47f926a4eb605d8e6074063))
+
+Tests: 2606 (+0 since 1.34.0)
+
 ## [1.34.0](https://github.com/event4u-app/agent-config/compare/1.33.0...1.34.0) (2026-05-10)
 
 ### Features

package/README.md

@@ -7,7 +7,7 @@ Give your AI agents an audit-disciplined orchestration contract — testing, Git
 > Your agent picks up the project's stack, runs tests, prepares PRs, fixes CI — and follows your team's coding standards while doing it. Stack-aware skill sets ship for PHP (Laravel · Symfony · Zend/Laminas), JavaScript (Next.js · React · Node), and cross-stack concerns (API · testing · security · observability).
 
 <p align="center">
-  <strong>167 Skills</strong> · <strong>60 Rules</strong> · <strong>103 Commands</strong> · <strong>68 Guidelines</strong> · <strong>8 AI Tools</strong>
+  <strong>173 Skills</strong> · <strong>60 Rules</strong> · <strong>103 Commands</strong> · <strong>69 Guidelines</strong> · <strong>8 AI Tools</strong>
 </p>
 
 ---
@@ -368,7 +368,7 @@ Every developer gets the same behavior. No per-user setup needed.
 native slash-commands)
 
 > **What this means in practice:** Augment Code and Claude Code get the full
-> package (rules + 167 skills + 103 native commands). Cursor, Cline, Windsurf,
+> package (rules + 173 skills + 103 native commands). Cursor, Cline, Windsurf,
 > Gemini CLI, and GitHub Copilot only get the **rules** natively; skills and
 > commands are available to them as documentation the agent can read, not as
 > first-class features.

package/docs/architecture.md

@@ -96,10 +96,10 @@ fails on any source-side violation, without producing artifacts.
 
 | Layer | Count | Purpose |
 |---|---|---|
-| **Skills** | 167 | On-demand expertise — stack analysis (Laravel · Symfony · Zend / Laminas · Next.js · React · Node), testing, Docker, API design, security, observability, … |
+| **Skills** | 173 | On-demand expertise — stack analysis (Laravel · Symfony · Zend / Laminas · Next.js · React · Node), testing, Docker, API design, security, observability, … |
 | **Rules** | 60 | Always-active constraints — coding standards, scope control, verification, language-and-tone, agent-authority |
 | **Commands** | 103 | Slash-command workflows — `/commit`, `/create-pr`, `/fix ci`, `/optimize skills`, `/feature plan`, `/work`, `/implement-ticket`, `/compress`, … |
-| **Guidelines** | 68 | Reference material cited by skills — PHP patterns, Eloquent, Playwright, agent-infra, … |
+| **Guidelines** | 69 | Reference material cited by skills — PHP patterns, Eloquent, Playwright, agent-infra, … |
 | **Templates** | 7 | Scaffolds for features, roadmaps, contexts, skills, overrides |
 | **Contexts** | 5 | Shared knowledge about the system itself |
 

package/docs/catalog.md

@@ -1,13 +1,13 @@
 # agent-config — Public Catalog
 
-Consumer-facing catalog of all **395 public artefacts** shipped by
+Consumer-facing catalog of all **398 public artefacts** shipped by
 this package. Internal package-maintenance rules and deprecation shims
 are excluded.
 
 > **Regenerate:** `python3 scripts/generate_index.py`
 > Auto-generated — do not edit manually.
 
-## Skills (167)
+## Skills (169)
 
 | kind | name | extra | description |
 |---|---|---|---|
@@ -41,6 +41,7 @@ are excluded.
 | skill | [`conventional-commits-writing`](../.agent-src/skills/conventional-commits-writing/SKILL.md) |  | Use when writing commit messages or squash-merge titles — `feat:`, `fix:`, `chore:`, scopes, breaking changes — even when the user just says 'commit this' without naming Conventional Commits. |
 | skill | [`copilot-agents-optimization`](../.agent-src/skills/copilot-agents-optimization/SKILL.md) |  | Use when optimizing AGENTS.md or copilot-instructions.md — deduplicates against .augment/ content, enforces line budgets, and focuses each file on its audience. |
 | skill | [`copilot-config`](../.agent-src/skills/copilot-config/SKILL.md) |  | Use when configuring GitHub Copilot — copilot-instructions.md, PR review patterns, output optimization — even when the user just says 'tune Copilot' or 'why is Copilot commenting on X'. |
+| skill | [`customer-research`](../.agent-src/skills/customer-research/SKILL.md) |  | Use when shaping a discovery slice — JTBD-framed interview guide, switch-event focus, verbatim quotes not summaries. Triggers on 'talk to users', 'why did they cancel', 'before we build X'. |
 | skill | [`dashboard-design`](../.agent-src/skills/dashboard-design/SKILL.md) |  | Use when designing monitoring dashboards — visualization selection, layout principles, observability strategies (RED/USE/Golden Signals), and data storytelling. |
 | skill | [`data-flow-mapper`](../.agent-src/skills/data-flow-mapper/SKILL.md) |  | Use BEFORE editing code that touches user data — traces the value from entry → validation → transformation → storage → egress, every hop cited with file:line. |
 | skill | [`database`](../.agent-src/skills/database/SKILL.md) |  | Use when working with database architecture, MariaDB/MySQL tuning, indexing strategies, slow queries, or multi-connection patterns — even when the user just says 'this query is slow'. |
@@ -136,6 +137,7 @@ are excluded.
 | skill | [`receiving-code-review`](../.agent-src/skills/receiving-code-review/SKILL.md) |  | Use when processing code review feedback (bot or human) before changing anything — triages, verifies, and pushes back with technical reasoning — even when the user just says 'fix the comments'. |
 | skill | [`refine-prompt`](../.agent-src/skills/refine-prompt/SKILL.md) |  | 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?'. |
 | skill | [`refine-ticket`](../.agent-src/skills/refine-ticket/SKILL.md) |  | Refine a Jira/Linear ticket before planning — 'refine ticket', 'tighten AC on PROJ-123', 'ist das Ticket klar?' — rewritten ticket, Top-5 risks, persona voices, sub-skills orchestrated, close-prompt. |
+| skill | [`release-comms`](../.agent-src/skills/release-comms/SKILL.md) |  | Use when turning a shipped changelog into a release narrative — value-not-feature framing, audience-segmented surfaces, one source of truth. Triggers on 'announce the release', 'write changelog post'. |
 | skill | [`repomix-packer`](../.agent-src/skills/repomix-packer/SKILL.md) |  | 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. |
 | skill | [`requesting-code-review`](../.agent-src/skills/requesting-code-review/SKILL.md) |  | Use when asking for a review or creating a PR — self-review first, frame the right context, test plan included — even when the user just says 'open a PR' or 'ready to merge'. |
 | skill | [`review-routing`](../.agent-src/skills/review-routing/SKILL.md) |  | Use when preparing a PR description, suggesting reviewers, or flagging risk — produces owner-mapped roles plus historical bug-pattern matches from project-local YAML. |
@@ -349,7 +351,7 @@ are excluded.
 | command | [`upstream-contribute`](../.agent-src/commands/upstream-contribute.md) |  | Contribute a learning, skill, rule, or fix from a consumer project back to the shared agent-config package |
 | command | [`work`](../.agent-src/commands/work.md) |  | 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. |
 
-## Guidelines (68)
+## Guidelines (69)
 
 | kind | name | category | description |
 |---|---|---|---|
@@ -389,6 +391,7 @@ are excluded.
 | guideline | [`verify-before-complete-demos`](../docs/guidelines/agent-infra/verify-before-complete-demos.md) | agent-infra |  |
 | guideline | [`augment-portability-patterns`](../docs/guidelines/augment-portability-patterns.md) | (root) |  |
 | guideline | [`code-clarity`](../docs/guidelines/code-clarity.md) | (root) |  |
+| guideline | [`cross-role-handoff`](../docs/guidelines/cross-role-handoff.md) | (root) |  |
 | guideline | [`readme-size-and-splitting`](../docs/guidelines/docs/readme-size-and-splitting.md) | docs |  |
 | guideline | [`playwright`](../docs/guidelines/e2e/playwright.md) | e2e |  |
 | guideline | [`api-design`](../docs/guidelines/php/api-design.md) | php |  |