@ikon85/agent-workflow-kit 0.26.1 → 0.27.0

package/.agents/skills/ask-matt/SKILL.md

@@ -90,8 +90,7 @@ An independent second model catches what one model rationalises. Read-only, boun
 
 Not feature work — upkeep.
 
-- **`/improve-codebase-architecture`** — run in spare moments to keep the codebase good for agents. Surfaces **deepening opportunities**; picking one _generates an idea_ for the main flow at `/grill-with-docs`.
-- **`/zoom-out`** — step back from the diff to the structure when a change is fighting the codebase; recon that becomes a planned slice or guides a refactor in place.
+- **`/improve-codebase-architecture`** — run in spare moments to keep the codebase good for agents, or step back from the diff to the structure when a change is fighting the codebase. Surfaces **deepening opportunities**; picking one _generates an idea_ for the main flow at `/grill-with-docs`.
 - **`/security-audit`** — a whole-app, application-layer security audit run as an independent two-model pass (two models audit the same code separately, then the remediation plan is hardened before any fix). Run before a release or after the attack surface changes (new endpoint, new input source, auth change, dependency bump). Infra hardening (ports/TLS/SSH/backups) is audited separately.
 
 ## Vocabulary underneath

package/.agents/skills/board-to-waves/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: board-to-waves
 disable-model-invocation: false
-"description": "Use when sweeping/grooming the GitHub backlog board to cluster open issues into thematic waves (Wellen) — \"lass uns das Board durchgehen\", \"was ist offen und passt zusammen\", \"clustern wir den Backlog\", \"welche Wellen stecken da drin\" — or to spot candidate waves before planning. Reads all open issues, groups them by the Gate+Booster+Splitter heuristic, estimates size/risk + grill-needed per candidate, and after the user confirms creates cluster/Wave-less candidate STUB issues with a To-Do checklist. STOPS at stubs: no PRD, no slicing, no sub-issue links, no promotion (downstream: to-prd matures the stub, to-issues slices + promotes). NOT for maturing/slicing ONE already-chosen candidate (to-prd/to-issues), NOT for per-issue triage labelling (triage), NOT for code comprehension (zoom-out) — this is board-WIDE thematic affinity grouping, not per-issue and not code-reading."
+"description": "Use when sweeping/grooming the GitHub backlog board to cluster open issues into thematic waves (Wellen) — \"lass uns das Board durchgehen\", \"was ist offen und passt zusammen\", \"clustern wir den Backlog\", \"welche Wellen stecken da drin\" — or to spot candidate waves before planning. Reads all open issues, groups them by the Gate+Booster+Splitter heuristic, estimates size/risk + grill-needed per candidate, and after the user confirms creates cluster/Wave-less candidate STUB issues with a To-Do checklist. STOPS at stubs: no PRD, no slicing, no sub-issue links, no promotion (downstream: to-prd matures the stub, to-issues slices + promotes). NOT for maturing/slicing ONE already-chosen candidate (to-prd/to-issues), NOT for per-issue triage labelling (triage), NOT for code comprehension — this is board-WIDE thematic affinity grouping, not per-issue and not code-reading."
 ---
 
 # board-to-waves
@@ -130,6 +130,6 @@ Next step (<maintainer>'s call, separate): grill → to-prd (matures the stub)
 
 ## Notes
 - **Stops at stubs.** Never write the PRD, slice, link, promote, or call `to-prd`/`to-issues` yourself.
-- Boundary: `triage` = per-issue state machine; `zoom-out` = code comprehension; `board-to-waves` = board-wide thematic affinity. Different altitudes.
+- Boundary: `triage` = per-issue state machine; `improve-codebase-architecture` = code structure; `board-to-waves` = board-wide thematic affinity. Different altitudes.
 - A leftover bucket is OK and intentional — not every issue belongs in a wave. Force-clustering dilutes the gate.
 - Size/risk are a rough estimate, not a commitment. <maintainer> can override the stub's "when to grill" recommendation at any time.

package/.agents/skills/improve-codebase-architecture/SKILL.md

@@ -8,8 +8,6 @@ description: "Find deepening opportunities in a codebase, informed by the domain
 
 Surface architectural friction and propose **deepening opportunities** — refactors that turn shallow modules into deep ones. The aim is testability and AI-navigability.
 
-For a quick one-off map of an unfamiliar area without the report/grilling loop below, use `zoom-out` instead.
-
 ## Glossary
 
 Use these terms exactly in every suggestion. Consistent language is the point — don't drift into "component," "service," "API," or "boundary." Full definitions in [LANGUAGE.md](LANGUAGE.md).

package/.agents/skills/setup-workflow/board-sync.md

@@ -71,6 +71,9 @@ The optional `wrapup` block is a wrapup-only switch, not a board field: `wrapup.
   "headings": {
     "vorBau": "Clarify Before Build"
   },
+  "titles": {
+    "wavePrefix": "Wave"
+  },
   "wrapup": {
     "remoteBranchSweep": false
   }
@@ -93,6 +96,14 @@ follows; renaming an option later is one edit here. A role you don't have
 with a visible hint, and `--status-role` commands fail with the exact snippet
 to add.
 
+### Wave titles (`titles.wavePrefix`)
+
+The word that opens a wave anchor's title: `<prefix> <N> — <topic>` (e.g.
+`Wave 7 — Auth hardening`). `board-sync.py promote` writes it and strips an
+existing one idempotently on re-promote. A profile **without** the key keeps
+the historical default `"Welle"`, so boards created before this key keep
+their titles unchanged; set it once to match your board's language.
+
 ## If the IDs are not yet filled (stub)
 
 1. Create a GitHub-Projects (v2) board for this owner and add the fields above (at minimum a `Status` single-select with your stage options — the recommended stage names are `Idea, Triaged, Spec, In Progress, Review, Done`, matching the seeded `roles` defaults).

package/.claude/skills/ask-matt/SKILL.md

@@ -90,8 +90,7 @@ An independent second model catches what one model rationalises. Read-only, boun
 
 Not feature work — upkeep.
 
-- **`/improve-codebase-architecture`** — run in spare moments to keep the codebase good for agents. Surfaces **deepening opportunities**; picking one _generates an idea_ for the main flow at `/grill-with-docs`.
-- **`/zoom-out`** — step back from the diff to the structure when a change is fighting the codebase; recon that becomes a planned slice or guides a refactor in place.
+- **`/improve-codebase-architecture`** — run in spare moments to keep the codebase good for agents, or step back from the diff to the structure when a change is fighting the codebase. Surfaces **deepening opportunities**; picking one _generates an idea_ for the main flow at `/grill-with-docs`.
 - **`/security-audit`** — a whole-app, application-layer security audit run as an independent two-model pass (two models audit the same code separately, then the remediation plan is hardened before any fix). Run before a release or after the attack surface changes (new endpoint, new input source, auth change, dependency bump). Infra hardening (ports/TLS/SSH/backups) is audited separately.
 
 ## Vocabulary underneath

package/.claude/skills/board-to-waves/SKILL.md

@@ -12,7 +12,7 @@ description: >-
   stubs: no PRD, no slicing, no sub-issue links, no promotion (downstream:
   to-prd matures the stub, to-issues slices + promotes). NOT for
   maturing/slicing ONE already-chosen candidate (to-prd/to-issues), NOT for
-  per-issue triage labelling (triage), NOT for code comprehension (zoom-out) —
+  per-issue triage labelling (triage), NOT for code comprehension —
   this is board-WIDE thematic affinity grouping, not per-issue and not
   code-reading.
 ---
@@ -143,6 +143,6 @@ Next step (<maintainer>'s call, separate): grill → to-prd (matures the stub)
 
 ## Notes
 - **Stops at stubs.** Never write the PRD, slice, link, promote, or call `to-prd`/`to-issues` yourself.
-- Boundary: `triage` = per-issue state machine; `zoom-out` = code comprehension; `board-to-waves` = board-wide thematic affinity. Different altitudes.
+- Boundary: `triage` = per-issue state machine; `improve-codebase-architecture` = code structure; `board-to-waves` = board-wide thematic affinity. Different altitudes.
 - A leftover bucket is OK and intentional — not every issue belongs in a wave. Force-clustering dilutes the gate.
 - Size/risk are a rough estimate, not a commitment. <maintainer> can override the stub's "when to grill" recommendation at any time.

package/.claude/skills/improve-codebase-architecture/SKILL.md

@@ -8,8 +8,6 @@ description: Find deepening opportunities in a codebase, informed by the domain
 
 Surface architectural friction and propose **deepening opportunities** — refactors that turn shallow modules into deep ones. The aim is testability and AI-navigability.
 
-For a quick one-off map of an unfamiliar area without the report/grilling loop below, use `zoom-out` instead.
-
 ## Glossary
 
 Use these terms exactly in every suggestion. Consistent language is the point — don't drift into "component," "service," "API," or "boundary." Full definitions in [LANGUAGE.md](LANGUAGE.md).

package/.claude/skills/setup-pre-commit/SKILL.md

@@ -102,3 +102,6 @@ both: pick one hooks mechanism per repo.
 - Hooks are just scripts — `echo`-debug them freely; nothing is hidden behind a
   tool.
 - Exit non-zero = block the commit. Exit 0 = allow.
+- Keep the template's `unset GIT_DIR …` line: git exports these to hooks, and a
+  gate that runs tests which call git in their own temp repos would otherwise
+  operate on the host repo's index instead.

package/.claude/skills/setup-pre-commit/scripts/pre-commit.template.sh

@@ -11,6 +11,12 @@
 
 set -euo pipefail
 
+# --- Env sanitize (keep this) ----------------------------------------------
+# Git exports GIT_DIR & co. to hooks. If your gate runs a test suite whose
+# child tests call git in their own temp repos, these inherited vars redirect
+# every such git call onto THIS repo's index (mass-staged deletions).
+unset GIT_DIR GIT_WORK_TREE GIT_INDEX_FILE GIT_PREFIX
+
 # --- Optional preflight ----------------------------------------------------
 # Bail early with a clear message if the toolchain isn't installed, so the
 # real checks don't fail with cryptic errors. Adapt or delete for your stack.

package/.claude/skills/setup-workflow/board-sync.md

@@ -71,6 +71,9 @@ The optional `wrapup` block is a wrapup-only switch, not a board field: `wrapup.
   "headings": {
     "vorBau": "Clarify Before Build"
   },
+  "titles": {
+    "wavePrefix": "Wave"
+  },
   "wrapup": {
     "remoteBranchSweep": false
   }
@@ -93,6 +96,14 @@ follows; renaming an option later is one edit here. A role you don't have
 with a visible hint, and `--status-role` commands fail with the exact snippet
 to add.
 
+### Wave titles (`titles.wavePrefix`)
+
+The word that opens a wave anchor's title: `<prefix> <N> — <topic>` (e.g.
+`Wave 7 — Auth hardening`). `board-sync.py promote` writes it and strips an
+existing one idempotently on re-promote. A profile **without** the key keeps
+the historical default `"Welle"`, so boards created before this key keep
+their titles unchanged; set it once to match your board's language.
+
 ## If the IDs are not yet filled (stub)
 
 1. Create a GitHub-Projects (v2) board for this owner and add the fields above (at minimum a `Status` single-select with your stage options — the recommended stage names are `Idea, Triaged, Spec, In Progress, Review, Done`, matching the seeded `roles` defaults).

package/.claude/skills/skill-manifest.json

@@ -167,15 +167,6 @@
       ],
       "provenance": "matt-pocock"
     },
-    "zoom-out": {
-      "class": "vendored",
-      "publish": true,
-      "surfaces": [
-        "claude",
-        "codex"
-      ],
-      "provenance": "matt-pocock"
-    },
     "improve-codebase-architecture": {
       "class": "vendored",
       "publish": true,
@@ -393,6 +384,7 @@
         "claude",
         "codex"
       ],
+      "installRole": "maintainer",
       "provenance": "own"
     },
     "project-release": {

package/PROVENANCE.md

@@ -6,7 +6,7 @@ not byte-identity.
 
 ## Matt Pocock (MIT) — https://github.com/mattpocock/skills @ d574778
 
-to-prd, to-issues, grill-with-docs, grill-me, tdd, diagnose, zoom-out,
+to-prd, to-issues, grill-with-docs, grill-me, tdd, diagnose,
 improve-codebase-architecture, prototype, triage, write-a-skill,
 codebase-design, domain-modeling, implement, resolving-merge-conflicts, ask-matt,
 wayfinder, research, git-guardrails-claude-code, setup-workflow.
@@ -15,9 +15,10 @@ Folder↔upstream-name divergence (upstream renamed; local folder kept for
 invocation stability): `diagnose` = upstream `diagnosing-bugs`,
 `write-a-skill` = upstream `writing-great-skills`, `to-prd` = upstream
 `to-spec`, `to-issues` = upstream `to-tickets` (upstream merged to-issues +
-the short-lived to-plan into to-tickets @ v1.1.0). `zoom-out` was removed
-upstream (attribution pins to its last-seen SHA 2bf7005) and is retained here
-as a local fork.
+the short-lived to-plan into to-tickets @ v1.1.0). `zoom-out` (last-seen
+upstream SHA 2bf7005) was removed upstream and, after a period as a local
+fork, removed from this kit as well — `improve-codebase-architecture` covers
+the step-back-to-the-structure door.
 
 Each carries a `THIRD-PARTY-NOTICES.md` with its upstream path.
 

package/README.md

@@ -58,22 +58,20 @@ The skills aren't a grab-bag — they're four phases of one loop, entered throug
 single funnel no matter where your work starts. Each phase below names the failure
 mode it removes and the skills that remove it.
 
-![The workflow loop: idea / plan / backlog / raw-issue all funnel through an optional grill into one uniform PRD, which to-issues decomposes into an atomic issue or a wave anchor; a gate clears any unknown, then Execute → Land → Learn, which compounds back into the next idea. Two further streams enter outside the funnel — a bug/anomaly through diagnose, and a code-fighting-the-structure change through zoom-out — both joining at Execute; a one-time repo-setup lane (setup-workflow, git-guardrails, setup-pre-commit) sits off the loop and installs the pre-commit/pre-push gate that Land relies on.](docs/workflow.png)
+![The workflow as a subway map — one row per route, all converging on the same implement → wrapup → retro spine: a scale-check router sizes unclear work; the main line runs idea through an optional grill, to-prd, to-issues and a gate into implement (which drives tdd inside), wrapup, retro; a grill line scales from none over grill-me and grill-with-docs up to the +codex variants; a codex line adds cross-model review and build; program and board lines fund numbered waves built by orchestrate-wave; repair (diagnose) and structure (improve-codebase-architecture) lines enter from broken or tangled work; a learn line routes retro's findings into config by weight. Interchanges: verify-spike / decision-gate before an unknown, prototype for an unclear path, local-ci plus pre-commit/pre-push hooks before landing, ask-matt when lost, and a one-time setup lane.](docs/workflow.png)
 
 <!--
-  The image above is a pre-rendered PNG, not a live Mermaid block, on purpose:
-  GitHub's Mermaid renderer clips long node labels, and an <img>-embedded SVG
-  can't render Mermaid's foreignObject node text (shows blank). A rasterised PNG
-  renders identically everywhere.
-  Source of truth: tools/agent-workflow-kit/assets/workflow.mmd
-  Regenerate after editing the source:
-    npx -y @mermaid-js/mermaid-cli \
-      -i tools/agent-workflow-kit/assets/workflow.mmd \
-      -o tools/agent-workflow-kit/assets/workflow.png \
-      -t dark -b '#0d1117' -s 3
-  build-kit.mjs copies assets/workflow.png -> dist-kit/docs/workflow.png.
+  The image above is a pre-rendered PNG, not live HTML, on purpose: GitHub
+  READMEs can't embed HTML pages, and a PNG renders identically everywhere.
+  Source of truth: docs/workflow.html (same design language as
+  docs/methodology.html). Regenerate after editing the source:
+    serve docs/ locally, open workflow.html?theme=dark in a 1160px-wide
+    viewport, take a full-page screenshot -> docs/workflow.png
+  The interactive version is linked below and published via GitHub Pages.
 -->
 
+**[view the workflow map →](https://ikon85.github.io/agent-workflow-kit/workflow.html)**
+
 
 ### 1. Plan — turn a vague idea into shaped, tracked work
 
@@ -155,7 +153,7 @@ enter outside the plan funnel and feed straight into Execute:
 - **`diagnose`** — a disciplined root-cause hunt for bugs (reproduce → isolate →
   fix → prove), not a guess-and-patch. Entered from a bug or anomaly, never the PRD
   funnel; the fix it lands flows on into Execute.
-- **`zoom-out` / `improve-codebase-architecture`** — step back from the diff to
+- **`improve-codebase-architecture`** — step back from the diff to
   the structure when a change is fighting the codebase. A recon stream that either
   becomes a planned slice (back through `to-issues`) or guides a refactor in place.
 
@@ -332,6 +330,29 @@ still reference. Flags: `--force` (overwrite pre-existing files on `init`),
 
 ## Release notes
 
+### 0.27.0
+
+- removed: `.agents/skills/zoom-out/SKILL.md`
+- removed: `.agents/skills/zoom-out/THIRD-PARTY-NOTICES.md`
+- removed: `.claude/skills/zoom-out/SKILL.md`
+- removed: `.claude/skills/zoom-out/THIRD-PARTY-NOTICES.md`
+- changed: `.agents/skills/ask-matt/SKILL.md`
+- changed: `.agents/skills/board-to-waves/SKILL.md`
+- changed: `.agents/skills/improve-codebase-architecture/SKILL.md`
+- changed: `.agents/skills/setup-workflow/board-sync.md`
+- changed: `.claude/skills/ask-matt/SKILL.md`
+- changed: `.claude/skills/board-to-waves/SKILL.md`
+- changed: `.claude/skills/improve-codebase-architecture/SKILL.md`
+- changed: `.claude/skills/setup-pre-commit/SKILL.md`
+- changed: `.claude/skills/setup-pre-commit/scripts/pre-commit.template.sh`
+- changed: `.claude/skills/setup-workflow/board-sync.md`
+- changed: `scripts/board-sync.py`
+- changed: `scripts/board_config.py`
+
+### 0.26.2
+
+- Metadata-only release.
+
 ### 0.26.1
 
 - changed: `.agents/skills/kit-update/SKILL.md`
@@ -739,14 +760,15 @@ still reference. Flags: `--force` (overwrite pre-existing files on `init`),
 
 ## What's in the box
 
-**42 skills** (Router: ask-matt — "which skill/flow fits?" · Plan: grill-me,
+**43 skills** (Router: ask-matt — "which skill/flow fits?" · Plan: grill-me,
 grill-with-docs, to-prd, to-issues, board-to-waves, triage, spec-self-critique,
 verify-spike, decision-gate, scale-check, to-waves, wayfinder, research · Execute: tdd, prototype, implement, orchestrate-wave ·
-Design/diagnose/refactor streams: diagnose, zoom-out,
+Design/diagnose/refactor streams: diagnose,
 improve-codebase-architecture, codebase-design, domain-modeling, security-audit · Land: wrapup,
 resolving-merge-conflicts, code-review, local-ci, git-worktree-recover, kit-release,
-project-release · Learn: retro, audit-skills, write-a-skill · Setup:
-setup-workflow, git-guardrails, setup-pre-commit · Codex cross-model: grill-me-codex,
+project-release, kit-update · Learn: retro, audit-skills, write-a-skill,
+memory-lifecycle · Setup:
+setup-workflow, git-guardrails, setup-pre-commit, census-update · Codex cross-model: grill-me-codex,
 grill-with-docs-codex, codex-review, codex-build),
 installed for both surfaces — `.claude/skills`
 (Claude Code) and `.agents/skills` (Codex) — plus `codex-adapter-sync`