@ikon85/agent-workflow-kit 0.33.0 → 0.34.0

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

@@ -1,17 +1,25 @@
 ---
 name: to-waves
 disable-model-invocation: true
-description: "Turn a Program-PRD's wave plan into fully planned, execute-ready wave anchors and slice leaves after one complete chat preview. Validates the graph, publishes every wave, runs the to-prd/spec-self-critique/to-issues maturity contract for each wave, models unresolved work as explicit gates, and audits counted readiness. Idempotent and crash-recoverable. Use on a Program-PRD over several waves. NOT for a single-wave feature (to-issues) or backlog clustering (board-to-waves)."
+description: "Internal Program graph engine behind the public to-issues Planning facade. Turns an explicitly identified Program-PRD into execute-ready wave anchors and slice leaves after one complete chat preview. Kept as a disabled compatibility entrypoint for existing explicit invocations; normal routing always selects to-issues."
 ---
 
-# to-waves — Unfold a Program-PRD's wave plan onto the board
+# to-waves — Internal Program graph engine
+
+This skill is an **Internal Program graph engine**, selected by `to-issues` only
+when the source carries explicit, coherent Program identity. It is not a second
+public Planning route. The disabled `/to-waves` invocation remains only as a
+compatibility entrypoint for existing callers and tests; it applies this same
+contract and should direct future normal use to `/to-issues`.
 
 Takes a **Program-PRD** — the native Sub-Issue anchor over a multi-wave program
 (Programm → Phase → Welle → Slice) — and turns its `## Wellenplan` chapter into
 **fully planned wave anchors + slice leaves** on the board. Pipeline position:
-`scale-check → grill → to-prd (program mode) → to-waves`, with the per-wave
-`to-prd → spec-self-critique → to-issues` maturity pass owned inside this run.
-The **grill and to-prd sit upstream**; to-waves runs once the Program-PRD exists.
+`scale-check → grill → to-prd (program mode) → to-issues`, with this internal
+engine owning the per-wave `to-prd → spec-self-critique → to-issues` maturity
+pass inside this run.
+The **grill and to-prd sit upstream**; the facade dispatches here once the
+Program-PRD exists and its identity is coherent.
 It **never invents structure** — it only unfolds what the plan already decided.
 
 <!-- readiness:required-preflight:start -->
@@ -24,8 +32,8 @@ node scripts/readiness.mjs check --skill to-waves --json
 ```
 
 - `verdict=ready`: continue with the existing workflow without announcing the check. **Ready is silent.**
-- `verdict=blocked`: `STOP` before any mutation. Report every required capability as `<capability>=<state>` so `issueTracker`, `managedBoard`, and `specCompleteness` failures — including distinct `missing`, `pending`, and `invalid` states — stay visible, then give exactly one recovery path: **Run `/setup-workflow`, then rerun `/to-waves`.** Do not fall back to bare tracker or board commands.
-- `managedBoard=not-applicable`: `STOP` and report that `/to-waves` is **inapplicable** for a project that deliberately has no managed board. This is a terminal project decision, not invalid evidence and not a partially active mode.
+- `verdict=blocked`: `STOP` before any mutation. Report every required capability as `<capability>=<state>` so `issueTracker`, `managedBoard`, and `specCompleteness` failures — including distinct `missing`, `pending`, and `invalid` states — stay visible, then give exactly one recovery path: **Run `/setup-workflow`, then rerun `/to-issues`.** Do not fall back to bare tracker or board commands.
+- `managedBoard=not-applicable`: `STOP` and report that Program planning through `/to-issues` is **inapplicable** for a project that deliberately has no managed board. This is a terminal project decision, not invalid evidence and not a partially active mode.
 <!-- readiness:required-preflight:end -->
 
 Board constants (project node, field/status IDs) + helpers live **consumer-side**:
@@ -43,10 +51,14 @@ is the parser.
 
 ## 1. Input — a Program-PRD
 
-The target is a Program-PRD issue: it carries the `<!-- prd: program -->` marker (or
-the program-type label) and a `## Wellenplan` table. Passed in / from context. If the
-issue is a plain feature-PRD or a Welle-Anchor, stop — a feature-PRD is `to-issues`'
-target, an anchor is already a single wave.
+The target is a Program-PRD issue: it carries both the
+`<!-- prd: program -->` marker and the configured Program-type label, plus a
+`## Wellenplan` table. Passed in from the facade or explicit compatibility
+invocation. If either identity half is missing, they disagree, or Feature
+identity is also present, stop before preview or write and return to
+`to-issues`; never infer Program mode from the table, prose, size, or model
+judgment. A plain Feature-PRD remains on the facade's Feature path; a
+Wave-Anchor is already a single wave.
 
 ## 2. Parse + validate — the graph preflight
 
@@ -316,7 +328,7 @@ python3 scripts/board-sync.py program-sync <prd#>
 ## Audit block (visible output)
 
 ```
-to-waves: prd=#<n> preview=<approved|rejected>
+to-issues: planning-mode=program engine=to-waves prd=#<n> preview=<approved|rejected>
   created=<stubs X von Y, leaves X von Y>  adopted=<#a #b … | none>
   stamped=<N von M Wave/Phase>  phase=<stamped | skipped (profile lacks fields.phase)>
   matured=<X von Y>  execute-ready=<X von Y Wellen ausführungsreif>

package/README.md

@@ -85,9 +85,11 @@ into the *same shaped artefact*: a Draft-PRD that, once sliced, becomes either o
 atomic issue or a wave anchor with child slices. What counts downstream is the
 **shape of the artefact, never where it came from** — so each step can be entered
 cold and *extracts or synthesizes* what's missing instead of assuming an earlier
-step ran. The routing key is just *"is there an issue yet?"*: a loose artefact
+step ran. The entry key is just *"is there an issue yet?"*: a loose artefact
 (no issue) enters at `to-prd`; an existing issue or file-bundle enters at
-`to-issues` directly.
+`to-issues` directly. Inside that facade, the explicit PRD identity — Feature or
+Program — is the only mode selector; a cold source must establish one before a
+remote write.
 
 - **Grill as deep as the work deserves — it's optional.** `grill-me` /
   `grill-with-docs` interrogate the intent (and your domain docs) until the real
@@ -98,13 +100,15 @@ step ran. The routing key is just *"is there an issue yet?"*: a loose artefact
   Draft-PRD issue, *extracting* the template sections from what already exists. A
   required section it genuinely can't derive becomes an honest **Open points**
   block, never a silent "looks complete" placeholder.
-- **`to-issues`** slices the PRD into tracer-bullet verticals and picks the shape:
-  **1 slice → one atomic issue** the PR closes; **≥2 slices → a wave anchor** with
-  linked child slices. It re-derives readiness from the artefact itself, so it works
-  just as well started straight on a raw issue or file-bundle — any unresolved
-  *Open points* travel through as a build-blocking gate (the profile's
-  configurable `vorBau` heading, see [Configuration](#configuration)) that never
-  vanishes silently.
+- **`to-issues`** is the single public Planning facade. Explicit Feature
+  identity selects tracer-bullet decomposition and picks the shape: **1 slice →
+  one atomic issue** the PR closes; **≥2 slices → a wave anchor** with linked
+  child slices. Explicit Program identity selects the existing internal graph
+  engine and preserves its complete chat preview before any board write.
+  Missing or contradictory identity stops before a write; size, prose, and model
+  judgment never select the mode. Any unresolved *Open points* travel through as
+  a build-blocking gate (the profile's configurable `vorBau` heading, see
+  [Configuration](#configuration)) that never vanishes silently.
 - **`board-to-waves`** clusters an existing backlog into themed campaigns when you
   need to *find* the next wave rather than start fresh.
 - **`triage`** keeps the inbox sane with a consistent label vocabulary.
@@ -211,7 +215,8 @@ hands a well-defined object to the level below:
 
 Two roads lead to the same wave. **Top-down:** `scale-check` names the size in
 a few plain questions; a big undertaking gets grilled once into a Program PRD
-with a wave plan, and `to-waves` unfolds it into named waves after you approve
+with a wave plan, and `to-issues` selects its internal Program graph path from
+that explicit identity. It unfolds the plan into named waves after you approve
 a full preview in chat — zero board writes until you say yes. **Bottom-up:**
 `board-to-waves` clusters loose issues into a wave candidate, which earns a
 real number only when you promote it. Either road lands in the *identical*
@@ -222,7 +227,7 @@ When the slices are file-disjoint and their specs are locked, **`orchestrate-wav
 lands the whole anchor end-to-end — often AFK: it dispatches an implementer per
 slice into its own worktree, integrates serially, verifies centrally, and lands
 the wave. It's the execute-and-land node of the wave ladder (`scale-check` →
-`to-waves` / `board-to-waves` → `orchestrate-wave`); a single slice still just
+`to-issues` / `board-to-waves` → `orchestrate-wave`); a single slice still just
 goes to `implement`.
 
 ![The Program-to-Phase-to-Wave-to-Slice altitude ladder, and the two routes — a planned top-down Program route and a grown bottom-up board route — that both fund the same Wave-and-Slices build spine.](docs/methodology.svg)
@@ -380,6 +385,69 @@ the old way. Decision record:
 
 ## Release notes
 
+### 0.34.0
+
+- added: `src/commands/routing-policy-update.mjs`
+- added: `src/lib/agentSurfaceRegistry.mjs`
+- added: `src/lib/dispatchReceipt.mjs`
+- added: `src/lib/frontendWorkloads.mjs`
+- added: `src/lib/routeDispatcher.mjs`
+- added: `src/lib/routingAccessGraph.mjs`
+- added: `src/lib/routingAdapters/claude.mjs`
+- added: `src/lib/routingAdapters/codex.mjs`
+- added: `src/lib/routingCatalog.mjs`
+- added: `src/lib/routingEvidenceCache.mjs`
+- added: `src/lib/routingIntent.mjs`
+- added: `src/lib/routingPolicy.mjs`
+- added: `src/lib/routingProfile.mjs`
+- added: `src/lib/routingResolver.mjs`
+- added: `src/lib/routingSources/artificialAnalysis.mjs`
+- added: `src/lib/routingSources/benchlm.mjs`
+- added: `src/lib/routingSources/codeArena.mjs`
+- added: `src/lib/routingSources/deepswe.mjs`
+- added: `src/lib/routingSources/openhands.mjs`
+- added: `src/lib/routingSources/openhandsFrontend.mjs`
+- changed: `.agents/skills/ask-matt/SKILL.md`
+- changed: `.agents/skills/audit-skills/SKILL.md`
+- changed: `.agents/skills/board-to-waves/SKILL.md`
+- changed: `.agents/skills/code-review/SKILL.md`
+- changed: `.agents/skills/codebase-design/DESIGN-IT-TWICE.md`
+- changed: `.agents/skills/codex-adapter-sync/SKILL.md`
+- changed: `.agents/skills/improve-codebase-architecture/INTERFACE-DESIGN.md`
+- changed: `.agents/skills/improve-codebase-architecture/SKILL.md`
+- changed: `.agents/skills/kit-update/SKILL.md`
+- changed: `.agents/skills/orchestrate-wave/SKILL.md`
+- changed: `.agents/skills/orchestrate-wave/references/dispatch-subagents.md`
+- changed: `.agents/skills/orchestrate-wave/references/dispatch-workflow.md`
+- changed: `.agents/skills/research/SKILL.md`
+- changed: `.agents/skills/scale-check/SKILL.md`
+- changed: `.agents/skills/setup-workflow/SKILL.md`
+- changed: `.agents/skills/setup-workflow/board-sync.md`
+- changed: `.agents/skills/setup-workflow/workflow-overview.md`
+- changed: `.agents/skills/to-issues/SKILL.md`
+- changed: `.agents/skills/to-waves/SKILL.md`
+- changed: `.claude/skills/ask-matt/SKILL.md`
+- changed: `.claude/skills/audit-skills/SKILL.md`
+- changed: `.claude/skills/board-to-waves/SKILL.md`
+- changed: `.claude/skills/code-review/SKILL.md`
+- changed: `.claude/skills/codebase-design/DESIGN-IT-TWICE.md`
+- changed: `.claude/skills/improve-codebase-architecture/INTERFACE-DESIGN.md`
+- changed: `.claude/skills/improve-codebase-architecture/SKILL.md`
+- changed: `.claude/skills/kit-update/SKILL.md`
+- changed: `.claude/skills/orchestrate-wave/SKILL.md`
+- changed: `.claude/skills/orchestrate-wave/references/dispatch-subagents.md`
+- changed: `.claude/skills/orchestrate-wave/references/dispatch-workflow.md`
+- changed: `.claude/skills/research/SKILL.md`
+- changed: `.claude/skills/scale-check/SKILL.md`
+- changed: `.claude/skills/setup-workflow/SKILL.md`
+- changed: `.claude/skills/setup-workflow/board-sync.md`
+- changed: `.claude/skills/setup-workflow/workflow-overview.md`
+- changed: `.claude/skills/to-issues/SKILL.md`
+- changed: `.claude/skills/to-waves/SKILL.md`
+- changed: `docs/agents/wave-anchor-template.md`
+- changed: `scripts/codex-exec.sh`
+- changed: `src/lib/capabilityMatrix.mjs`
+
 ### 0.33.0
 
 - added: `.agents/skills/orchestrate-wave/references/dispatch-subagents.md`