@event4u/agent-config 7.4.0 → 8.0.0

package/dist/agent-src/skills/logo-generation/SKILL.md

@@ -1,7 +1,7 @@
 ---
 model_tier: inherit
 name: logo-generation
-description: "Generate a logo or brand mark — structured prompt + provider routing, with a true-vector path via a vector-native provider or LLM-authored SVG for simple marks. Use for logo or brand mark generation."
+description: "Generate a logo or brand mark — structured prompt + provider routing, with a true-vector path (vector-native provider or LLM-authored SVG). Use for logo or brand mark generation."
 domain: product
 personas:
   - design-director

package/dist/agent-src/skills/markitdown/SKILL.md

@@ -1,7 +1,7 @@
 ---
 model_tier: medium
 name: markitdown
-description: "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'."
+description: "Convert PDF, DOCX, XLSX, PPTX, EPUB, images, or audio to Markdown via the markitdown-mcp server — 'extract this PDF', 'OCR this image', 'transcribe this audio'."
 status: active
 tier: senior
 domain: process

package/dist/agent-src/skills/md-language-check/SKILL.md

@@ -9,8 +9,8 @@ execution:
   timeout_seconds: 30
   allowed_tools: []
   command:
-    - python3
-    - scripts/check_md_language.py
+    - ./scripts-run
+    - src/scripts/check_md_language
 workspaces:
   - agent-config-maintainer
 packs:
@@ -114,7 +114,7 @@ proceeds on exit `0`.
 ## Do NOT
 
 - Do NOT silence the checker by deleting trigger words from
-  `scripts/check_md_language.py`; extend the allow-list (anchor
+  `src/scripts/check_md_language.ts`; extend the allow-list (anchor
   blocks, ignore marker) instead
 - Do NOT add the ignore marker to body prose just to push a save
   through; the marker is for meta-documentation that quotes tokens,

package/dist/agent-src/skills/memory-consolidation/SKILL.md

@@ -101,9 +101,35 @@ miner is too loose; tighten patterns and re-run before promoting.
    curated YAML (next phase) become team-shared (committed).
 3. Default to `--preview` mode: render the JSONL block to stdout and
    stop. Only `--commit-intake` writes the file.
+4. **Triage each fact NOT already promoted to curated YAML** against
+   `agents/knowledge/{concepts,procedures}/` before treating it as
+   brand new:
+
+   | Triage | Condition | Action |
+   |---|---|---|
+   | `NEW` | No existing knowledge page covers this topic | Candidate for a new page (via `/team-knowledge consolidate`, not this skill) |
+   | `EXTEND` | An existing page covers the topic but is missing this detail | Note the target page in the report; do not edit mid-cycle |
+   | `CONFIRM` | An existing page already states this exactly | Discard — no duplicate entry |
+   | `CONFLICT` | An existing page states the opposite or a stale variant | Record **both** positions verbatim in the report with a `contested: true` recommendation for that page — never silently overwrite; resolution is always human |
+
+5. **Track cross-cycle recurrence toward skill-candidacy.** For each
+   `NEW` fact, run:
+
+   ```bash
+   ./scripts-run src/scripts/update_skill_candidates --topic "<stable-slug>" --session "<session-id>" --date "<YYYY-MM-DD>"
+   ```
+
+   This increments a durable per-topic counter in
+   `agents/knowledge/procedures/skill-candidates.md` — a fact that
+   recurs unpromoted across ≥ 3 consolidation cycles becomes a live
+   candidate the exit report surfaces for
+   [`learning-to-rule-or-skill`](../learning-to-rule-or-skill/SKILL.md)
+   to pick up. This script only counts; it never proposes or writes
+   the skill/rule itself. Regenerate `agents/knowledge/INDEX.md`
+   (`generate_knowledge_index.ts`) after any candidate update.
 
 **Exit gate:** every fact carries ≥ 1 tag and a JSONL-shape that
-validates against the contract.
+validates against the contract; every fact has a triage verdict.
 
 ### Phase 4 — PRUNE & INDEX
 
@@ -143,6 +169,15 @@ skills — github.com/ViktorAxelsen/MemSkill, Apache-2.0, commit `9907c35f8cc7`)
   reusable facts, not transcripts or one-off chatter.
 - **One durable fact per entry.** No narrative blobs — each entry is a single
   PATTERN / CONVENTION / INVARIANT / GOTCHA the next agent can act on.
+- **"Don't relitigate" memories carry scope + `revisit-if`.** A memory that
+  locks a question as settled — an honest-null verdict, a council convergence,
+  a maintainer call — is not a permanent law; it is a decision under the
+  conditions that held when it was written. Record what exactly is settled
+  (narrow enough that a different-but-similar proposal is not silently
+  covered) and at least one concrete condition that reopens it. Tag whether
+  it is **settled-by-evidence** (an eval ran) or **settled-by-decision** (a
+  maintainer call) — the latter is cheaper to reopen. See
+  [`decision-revisit-gate`](../../rules/decision-revisit-gate.md).
 
 This is **meta-memory**: the skill of *how to remember* (what to extract,
 keep, forget) — distinct from the remembered content. The store stays simple
@@ -151,6 +186,36 @@ INSERT/UPDATE/DELETE/NOOP operation machinery (append-only JSONL + curated
 YAML need no such ops) and do **not** import any retrieval / decay / trust
 engine.
 
+## Applying recalled memories
+
+How memories are *written* is covered above; this section covers how
+recalled content is *used* once retrieved.
+
+- **Apply selectively and contextually.** A recalled fact surfaces only
+  when it's relevant to the current turn — not as a demonstration that
+  memory exists.
+- **Never narrate the retrieval mechanism.** Forbidden phrases: "I
+  remember", "based on your memories", "according to your profile/data",
+  "I can see from memory". Recalled facts surface as normal working
+  knowledge, indistinguishable in tone from anything else the agent knows.
+- **Sensitivity floor.** Recalled content about sensitive topics
+  (personal difficulties, conflicts, health) is never surfaced
+  unprompted — only when the user raises the topic first, this session.
+  Bringing up a sensitive memory unprompted is not just unhelpful, it is
+  actively harmful.
+- **Staleness still applies.** A recalled memory reflects what was true
+  when it was written — verify referenced files/flags/state still hold
+  before treating it as current (see the memory-and-other-persistence
+  guidance this skill's callers already carry).
+
+### Retrieval-trigger linguistics
+
+Before answering from scratch, treat these as signals to consult memory
+first: possessives ("my/our X"), definite references to unnamed prior
+work ("that bug", "the migration"), and past-time cues ("last week",
+"back then"). These phrasings imply the user expects continuity with
+something already known, not a first-time explanation.
+
 ## TranscriptAdapter contract
 
 The miner is host-agnostic by design. A `TranscriptAdapter` for host

package/dist/agent-src/skills/migration-architect/SKILL.md

@@ -5,6 +5,7 @@ description: "Use when shaping a non-trivial migration — rollout phases, dual-
 personas:
   - backend-architect
   - senior-engineer
+  - data-integrity
 domain: process
 workspaces:
   - engineering

package/dist/agent-src/skills/module-detect-on-the-fly/SKILL.md

@@ -67,8 +67,8 @@ Confirm both flags via `get_modules_config()` before running detection.
 
    - **Option 1** — build the payload (matches `propose_modules_config.py
      --json` shape, includes `detection_acknowledged: true`), pipe into
-     `python3 scripts/apply_modules_config.py --project <root>`.
-   - **Option 2** — run `python3 scripts/apply_modules_config.py
+     `./scripts-run src/scripts/apply_modules_config --project <root>`.
+   - **Option 2** — run `./scripts-run src/scripts/apply_modules_config
      --project <root> --acknowledge-only`. Flips only the ack flag;
      every other `modules.*` key stays untouched.
    - **Option 3** — list candidates, then loop back to step 3.

package/dist/agent-src/skills/performance-analysis/SKILL.md

@@ -2,6 +2,8 @@
 model_tier: high
 name: performance-analysis
 description: "ONLY when user explicitly requests: performance audit, bottleneck analysis, or N+1 query detection. NOT for regular feature work."
+personas:
+  - performance-engineer
 domain: discovery
 workspaces:
   - engineering

package/dist/agent-src/skills/prediction-pool-optimizer/SKILL.md

@@ -145,9 +145,9 @@ Don't hand-pick a scoreline. Run the executed grid optimiser — builds the full
 Poisson score grid, returns the EV-max tip under the step-1 point tiers:
 
 ```bash
-python3 scripts/prediction-pool/score_ev.py --lh <home-xg> --la <away-xg> \
+./scripts-run src/scripts/prediction-pool/score_ev --lh <home-xg> --la <away-xg> \
     --tendency <t> --diff <d> --exact <e>          # one match
-python3 scripts/prediction-pool/score_ev.py matches.json \
+./scripts-run src/scripts/prediction-pool/score_ev matches.json \
     --tendency <t> --diff <d> --exact <e>          # batch, prints a ranked table
 ```
 
@@ -176,7 +176,7 @@ of the field)**; pure EV-max converges with the crowd, can't open a gap.
 Measure it with the executed field simulator, not a "rough Kelly" hand-wave:
 
 ```bash
-python3 scripts/prediction-pool/pool_winsim.py pool.json --runs 4000 --max-flips 4
+./scripts-run src/scripts/prediction-pool/pool_winsim pool.json --runs 4000 --max-flips 4
 ```
 
 Models the field as softmax-EV tippers, reports `P(win)` for EV-max-everywhere,
@@ -204,7 +204,7 @@ question type — full taxonomy + per-type method in
   winner") aggregated per step 2, **or** the executed Poisson simulator:
 
   ```bash
-  python3 scripts/prediction-pool/poisson_sim.py <teams-xg.json> --runs 20000
+  ./scripts-run src/scripts/prediction-pool/poisson_sim <teams-xg.json> --runs 20000
   ```
 
   It plays the bracket from per-team expected goals and prints empirical

package/dist/agent-src/skills/premortem/SKILL.md

@@ -1,18 +1,15 @@
 ---
 name: premortem
 description: "Use before committing to a heavy or irreversible plan — imagine it's 6 months later and this failed; enumerate why, score each mode, derive early-warning signals and preventive guardrails."
-source: package
 domain: quality
 model_tier: high
 workspaces:
   - engineering
 packs:
   - analysis-workbench
-lifecycle: active
 trust:
   level: professional
   confidence: medium
-  human_review_required: false
 install:
   default: false
   removable: true

package/dist/agent-src/skills/project-analysis-core/SKILL.md

@@ -129,6 +129,22 @@ Check:
 6. Known uncertainties
 7. Recommended next specialist skill
 
+## Knowledge capture (`convention_detected` events)
+
+An architecture-map or stack finding that recurs (naming convention,
+module boundary, layering rule) is worth persisting for the team.
+Append to the knowledge intake instead of leaving it in the one-off
+analysis output — applies to every `project-analysis-*` specialist
+this skill hands off to:
+
+```bash
+./scripts-run src/scripts/emit_knowledge_event --type convention_detected \
+    --pattern "<pattern>" --evidence "file:line" --sample-size <N> --scope project
+```
+
+`/team-knowledge consolidate` turns accumulated events into
+`agents/knowledge/concepts/` pages as a reviewed batch.
+
 ## Gotcha
 
 * If versions are guessed, the whole analysis becomes unreliable.

package/dist/agent-src/skills/react-shadcn-ui/SKILL.md

@@ -125,6 +125,20 @@ declared version:
 - Streaming / partial-prerender boundaries — use the project's framework
   patterns (Next.js / Remix), not shadcn/ui.
 
+## Registry & MCP awareness (opt-in)
+
+Default path = bundled `scripts/shadcn_add.ts` + `components.json`; works on most projects, stays default. Modern registry model is OPT-IN — no round-trips on every op. JSON-schema + namespace detail lazy-loaded from [`reference/registry.md`](reference/registry.md); read only on this path.
+
+**`shadcn info --json` handshake** — run as grounding step WHEN `components.json` declares custom/namespaced `registries`, OR theme-alignment in scope. Returns framework / aliases / installed components / icon lib / base settings. NOT a forced first action on every `add` (over-gating, low ROI vanilla).
+
+- **Precedence:** prefer live `shadcn info --json`; fall back to `state.ui_audit.shadcn_inventory` (existing-ui-audit) when CLI/MCP unreachable. Live read wins.
+
+**Namespaced installs** — `@ns/item` resolves via the `registries` map to a `registry-item.json` URL (see reference). `view @ns/item` before `add`. Honour `registryDependencies` (install the graph, incl. version-pinned GitHub refs `acme/ui/button#v1.2.0`); keep propose-never-silent-run + `--dry-run`.
+
+**Token-aware scaffolding** — `registry-item.json` `cssVars` (OKLCH light/dark/theme) → align to project tokens (`info --json` / `components.json` / `state.ui_audit.design_tokens`); never inject the default shadcn neutral theme (flagged anti-slop tell: default theme + Inter + neutral grays).
+
+**MCP path (opt-in)** — shadcn MCP server: browse / search-across-registries / install-with-NL over MCP; wire per [`mcp`](../mcp/SKILL.md). Alternative to CLI, never a hard dep. Decision: CLI = default + universal; MCP = opt-in when configured; registry-JSON literacy underpins both.
+
 ## Procedure: render a shadcn/ui component for the design brief
 
 ### Step 0: Inspect
@@ -234,6 +248,10 @@ synthesise the updated `state.ui_review.findings` (including any
 remaining `a11y_violation` entries) so the engine's gate sees the
 current state on the next polish round.
 
+## Taste Dials
+
+`DESIGN.md` `## Taste Dials` → honour: Variance → layout-family spread + asymmetry; Motion → animation budget + reduced-motion posture; Density → spacing scale + info-per-viewport. Absent → follow brief's inferred dials.
+
 ## Do NOT
 
 - Do NOT install `shadcn-ui` from npm — primitives are scaffolded.

package/dist/agent-src/skills/react-shadcn-ui/reference/registry.md

@@ -0,0 +1,59 @@
+# shadcn registry & namespace reference
+
+> Lazy-loaded by `react-shadcn-ui` ONLY on the registry/MCP path (custom or
+> namespaced registries, or theme-alignment). Not in the always-on skill body —
+> zero token cost on the vanilla `shadcn add` path.
+
+## `registry-item.json` — the self-describing component unit
+
+Each item is a JSON doc the agent reads before scaffolding — never guesses
+paths, deps, or tokens.
+
+- `name` — item id.
+- `type` — one of: `registry:ui`, `registry:component`, `registry:block`,
+  `registry:hook`, `registry:lib`, `registry:theme`, `registry:style`,
+  `registry:page`, `registry:file`, `registry:base`, `registry:item`.
+- `dependencies` / `devDependencies` — npm packages.
+- `registryDependencies` — other items to pull first (the dependency graph):
+  built-in (`"button"`), namespaced (`"@acme/input"`), GitHub
+  (`"acme/ui/button#v1.2.0"`), URL, or local path.
+- `files[]` — each `{ path, type, target }`; `target` uses the project alias
+  placeholders (`~`, `@ui/`, `@lib/`, `@hooks/`) from `components.json`.
+- `cssVars` — tokens scoped by mode: `theme` (font/radius), `light`, `dark`,
+  OKLCH. **Align to the project's tokens; do not inject the default neutral
+  theme** (anti-slop C1/C5/T7).
+- `css` — raw `@layer` / `@utility` / `@keyframes` / `@plugin`.
+
+Scaffold order: read item → install npm `dependencies` → resolve
+`registryDependencies` (recurse) → write `files[]` to alias targets → merge
+`cssVars` into the project token layer (reconcile, don't overwrite).
+
+## Namespaced registries
+
+`components.json` maps a namespace → URL template under `registries`:
+
+```json
+{
+  "registries": {
+    "@acme-ui": "https://registry.acme.com/ui/{name}.json",
+    "@acme-auth": {
+      "url": "https://registry.acme.com/auth/{name}.json",
+      "headers": { "Authorization": "Bearer ${ACME_TOKEN}" }
+    }
+  }
+}
+```
+
+- Resolution: `@ns/name` → look up `@ns` → substitute `{name}` (+ optional
+  `{style}`). Reference regex: `^(@[a-zA-Z0-9](?:[a-zA-Z0-9-_]*[a-zA-Z0-9])?)\/(.+)$`.
+- Auth registries: per-registry `headers` with `${ENV_VAR}` — never inline a
+  token; read from the environment.
+- Namespace space is **decentralized** — no central collision authority; the
+  `components.json` map is the project's source of truth.
+
+## CLI surface (the agent drives these)
+
+`init` · `add [item|@ns/item]` · `search @ns -q <q>` · `view @ns/item` (inspect
+JSON before install) · `docs [item] --json` · `diff` (drift vs updated
+registry) · `info --json` (project context — see the SKILL handshake) · `build`
+(publish). Inspect with `view` before `add` — evidence before action.

package/dist/agent-src/skills/reasoning-orchestrator/SKILL.md

@@ -71,7 +71,9 @@ coordinates.
 Each link **delegates** to the artifact that owns it (no duplication):
 
 1. **ground** — close constraints/tools/info-gaps before designing
-   ([`think-before-action` § Environment grounding](../../rules/think-before-action.md)).
+   ([`think-before-action` § Environment grounding](../../rules/think-before-action.md));
+   seed the read from the **repo** slot of the
+   [context-spine](../../../docs/contracts/context-spine.md) when present.
 2. **intent** — state the inferred goal + one recommendation, standard host only
    ([`improve-before-implement` § Intent inference](../../rules/improve-before-implement.md)).
 3. **notes** — hypotheses/predictions/decisions/uncertainty to the notes file, not

package/dist/agent-src/skills/refine-ticket/SKILL.md

@@ -1,7 +1,7 @@
 ---
 model_tier: inherit
 name: "refine-ticket"
-description: "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."
+description: "Refine a Jira/Linear ticket before planning — 'refine ticket', 'tighten AC on PROJ-123', 'ist das Ticket klar?'; rewritten ticket, risks, persona voices, close-prompt."
 personas:
   - developer
   - senior-engineer
@@ -304,6 +304,10 @@ Per user interaction rules, accept number or free text. `editmeta`
 is cheap and cacheable; cache the result per Jira project key for
 the session, re-probe on project change.
 
+## Rubric pass (optional, surfacing-only)
+
+After refinement, run [`judge-artifact-completeness`](../judge-artifact-completeness/SKILL.md) with rubric `ticket-quality-score` to verify DoR readiness — AC, test plan, risk, estimate. Invoke when user asks for DoR check — not automatically.
+
 ## Output format
 
 1. **Refined ticket** section with rewritten title + description, wrapped in a copyable markdown block.

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

@@ -1,7 +1,7 @@
 ---
 model_tier: inherit
 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'."
+description: "Turn a shipped changelog into a release narrative — value-not-feature framing, audience-segmented surfaces. Triggers on 'announce the release', 'write changelog post'."
 status: active
 tier: senior
 domain: product
@@ -21,77 +21,77 @@ install:
 
 ## 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.
+- A release is shipping that contains user-facing change and the team is about to send a feature-list email.
+- A changelog draft reads like a commit log — engineering-honest, but unparseable for the user.
+- Multiple comms surfaces (in-app, email, social, docs) are about to be written by different people from the 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**.
+deprecation announcements that need legal sign-off, or pre-release
+discovery — this skill assumes the 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
+- **Mental model 16 — Leading vs. lagging indicators.** A release
+  note is the lagging artifact; the leading version is the in-app
+  prompt that fired before the user found the 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.
+- **Value-not-feature heuristic.** Every paragraph passes the *"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.
+1. Read the merged PR list / changelog block / release branch diff. The release is the **what**; comms is the **so what**. Conflate the two and you ship marketing.
+2. Read the **product** and **team** slots of the [context-spine](../../../docs/contracts/context-spine.md) (if the consumer project has filled them) for bounded scope and release cadence — surface choice depends on cadence (weekly: in-app + log; quarterly: email + post; major: all four).
+3. Identify the **single dominant change** the release ships. A release with 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.
+1. Three audiences max: **active user**, **at-risk / lapsed user**, **prospect**. More segments fragment the message; fewer hides the routing.
+2. Per audience, write one sentence: *"After this release, you can …"* completing with a user-side verb, not a product-side feature.
+3. If two audiences end up with the same sentence, collapse them — segmentation that does not change the message is 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).
+4. **Social / blog** — prospect; the **why**, not the **what** — frame against the user job (cite [`customer-research`](../customer-research/SKILL.md) if a switch-event surfaced).
 
-Cut surfaces aggressively. Weekly release does not need blog post.
+Cut surfaces aggressively. A weekly release does not need a 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.
+1. Open the changelog. Per surface, copy the dominant change line, then **rewrite the verb subject** from "we" to "you".
+2. Strip qualifiers ("now", "even better", "lightning-fast"). They are noise, not signal.
+3. Run the *"so the user can ___"* completion on every paragraph. Failing paragraphs are 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.
+1. Every claim links back to a changelog row or a doc URL. Unsourced claim → cut.
+2. No tense games — past for shipped, future for coming-soon (and only if the date is committed). "Roadmap" lives outside this skill.
+3. Names match the product surface. If the in-app says "Reports" and the email says "Insights", the user fires the 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.
+1. Produce the four artifacts (see `## Output`).
+2. Hand to whoever owns the 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.
+- The change is **shipped** and needs to reach existing users.
+- Multiple comms surfaces will be written by different people from the same source.
+- The team is about to default to a 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).
+- Production incident comms — route to [`incident-commander`](../incident-commander/SKILL.md).
+- Pre-release discovery / validation — route to [`customer-research`](../customer-research/SKILL.md).
+- Funnel-stage diagnostics post-release — route to [`funnel-analysis`](../funnel-analysis/SKILL.md).
+- Ranking which release to comms next — route to [`rice-prioritization`](../rice-prioritization/SKILL.md).
 
 ## When the agent should load this
 
@@ -104,29 +104,30 @@ Cut surfaces aggressively. Weekly release does not need blog post.
 ## 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)).
+2. **`changelog-entry.md`** — engineer-honest, dense, link-heavy block ready to paste into the project's changelog.
+3. **`comms-pack.md`** — per-surface drafts (in-app prompt, email, optional social/blog), each ≤ the 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 the senior PO ([`product-owner`](../../personas/product-owner.md); senior persona shipping in next plate).
 
 ## 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.
+- The default failure mode is feature-list email — written to make engineering feel seen, not to help the user.
+- Marketing puffery ("revolutionary", "delightful") fails the source check; cut on sight.
+- Two surfaces using different names for the same thing is the highest-frequency support-ticket trigger after a 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.
+- Do NOT promote a coming-soon item alongside shipped items — the user cannot tell which is which and stops trusting the next note.
+- Do NOT let a long-tail change steal the headline — the dominant change earns the headline, the long tail goes in the changelog.
+- Do NOT ship surfaces without the truth-check pass; an unsourced claim survives in social longer than the release does.
+- Do NOT paste more than a short excerpt from a linked source (commit message, PR body, issue thread) — `content-quoting-floor` caps verbatim quotes at 15 words, one per source; paraphrase the rest.
 
 ## 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).
+- Audiences: active user (will use it), at-risk (export friction was a 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.
+- Surfaces: changelog (full), in-app prompt to active users on next month-end, email to at-risk cohort with the same sentence and one CTA. No social.
+- Truth-check: claim links to the export PR; "one click" is literal — verified against the shipped UI.

package/dist/agent-src/skills/roadmap-management/SKILL.md

@@ -212,6 +212,16 @@ unfamiliar codebases.
 
 ### Executing a roadmap
 
+0. Read `execution.mode` from the roadmap frontmatter
+   (`autonomous` | `phase-checkpoints` | `interactive`; absent =
+   `interactive`). Under `/roadmap:process-*` the mode selects the
+   interaction pattern via the run-start execution contract — see
+   [`roadmap-execution-contract`](../../contexts/execution/roadmap-execution-contract.md).
+   The manual flow below describes `interactive`; under `autonomous`
+   / `phase-checkpoints` step 4's per-step ask is replaced by the
+   accepted contract. **Mode never changes archival semantics** —
+   glyph counting, the closure decision table, and the Iron Law 3
+   deferred-resolution gate below apply identically in every mode.
 1. Read the full roadmap.
 2. Find the next unchecked step (`- [ ]`).
 3. Summarize what needs to be done.
@@ -455,6 +465,21 @@ No global tooling required.
 
 The dashboard is a **read-only snapshot**. Do not edit it by hand — regenerate it.
 
+### Blockers on the dashboard
+
+Overview table's `Blocker` column counts each roadmap's open
+`## Blockers` entries (or legacy `> Blocked until` note), links to
+per-roadmap breakdown, which lists every open blocker with owner,
+blocked scope, full instructions. Authoring shape:
+[`templates/roadmaps.md` rule 20](../../agent-src/templates/roadmaps.md);
+authoring guidance: [`roadmap-writing § 5b`](../roadmap-writing/SKILL.md).
+Clearing a blocker flips `Status: resolved`, regenerates dashboard in
+same reply — same cadence as a checkbox flip.
+
+## Rubric pass (optional, surfacing-only)
+
+After producing roadmap, run [`judge-artifact-completeness`](../judge-artifact-completeness/SKILL.md) with rubric `roadmap-score` to surface missing dimensions (risk, tests, migration, maintainability). Score is a recommendation; never blocks shipping. Invoke only when user wants completeness check — not by default.
+
 ## Output format
 
 1. Roadmap file in agents/roadmaps/ with ordered phases and tasks

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

@@ -1,7 +1,7 @@
 ---
 model_tier: inherit
 name: roadmap-writing
-description: "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'."
+description: "Use when authoring or rewriting a roadmap in agents/roadmaps/ — phases, goal, acceptance criteria, council notes; fires even on 'write a plan for X' / 'draft a roadmap'."
 domain: process
 workspaces:
   - agent-config-maintainer
@@ -84,6 +84,25 @@ and council-pass notes capture the *why*; checkboxes capture the
 [`roadmap-progress-sync`](../../rules/roadmap-progress-sync.md)
 Iron Law #2.
 
+### 4b. Declare the execution mode (frontmatter)
+
+Every new roadmap declares how a later `/roadmap:process-*` run should
+interact, via `execution.mode:` in frontmatter — `autonomous` (one
+run-start execution-contract confirmation, then uninterrupted except
+safety floors), `phase-checkpoints` (halt + compact status per phase
+boundary), or `interactive` (absent-field default; omit field).
+Semantics: [`templates/roadmaps.md` rule 19](../../templates/roadmaps.md);
+run mechanics:
+[`roadmap-execution-contract`](../../contexts/execution/roadmap-execution-contract.md).
+Field is intent, never a permission grant — grants happen only at the
+run-start contract. `/roadmap:create` asks this as one question; when
+authoring a roadmap directly, ask it too (follow-ups pre-select the
+parent's mode but always re-ask). **Authoring duty for `autonomous`:**
+steps must be precise enough to clear `ask-when-uncertain` vague-
+trigger patterns — vagueness resolved at authoring time, not mid-run;
+pre-existing `[~]` items in an `autonomous` roadmap draw a lint
+warning (they guarantee the archival gate fires later).
+
 ### 5. Exit & rollback per phase
 
 Each phase declares **exit criteria** (decidable signals that the
@@ -91,6 +110,17 @@ phase is done) and **rollback** (what to revert if the phase fails).
 A phase without exit criteria is open-ended; a phase without
 rollback assumes success.
 
+### 5b. Blockers are structured, not free prose
+
+Gate only user or maintainer can clear — decision, external
+dependency, evidence threshold, kernel-budget soak window — records
+as `## Blockers` entry (`### blocker: <id>` with `Status` / `Owner` /
+`Blocks` / `What to do` / `Resolved when`), never a stray "blocked on
+X" sentence. Dashboard generator parses these into overview's
+`Blocker` column and per-roadmap breakdown. Full shape:
+[`templates/roadmaps.md` rule 20](../../agent-src/templates/roadmaps.md).
+Omit section entirely when roadmap has no such gate.
+
 ### 6. Step-marker semantics — pick `[~]` (defer) vs `[-]` (cancel) honestly
 
 Difference carries load when authoring (and especially when rewriting
@@ -166,7 +196,7 @@ capabilities into the suite:
 
 Ordinary internally-originated roadmap → **skip this section**; §§ 0–7
 are the whole job. Don't bolt a Provenance block or gap-table onto a
-plan needing neither (template rule 18).
+plan needing neither (template rule 19).
 
 When it fires, add four moves to §§ 0–7:
 
@@ -282,7 +312,7 @@ to every roadmap you author.
   skill dump, not integration.
 * Add a `## Provenance` block (or gap-table) to an **internally
   originated** roadmap — § 8 is conditional; an empty Provenance section
-  is noise (template rule 18).
+  is noise (template rule 19).
 * Name the raw competitor / tool in a tracked roadmap, or paste a raw
   source link — anonymize + `ENC1:`-encrypt
   ([`source-confidentiality`](../../rules/source-confidentiality.md)).