@ikon85/agent-workflow-kit 0.34.6 → 0.35.0

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

@@ -3,6 +3,14 @@ name: setup-pre-commit
 description: Set up a native, zero-dependency git pre-commit hook (via core.hooksPath) that runs your project's type checks, linting, tests, or formatting before each commit. Use when the user wants to add pre-commit hooks, gate commits on checks, or wire commit-time typecheck/lint/test/format — no Husky or Node deps required.
 ---
 
+<!-- project-extension:protocol-v1:start -->
+## Project extension
+
+Before applying this Core skill, run `node scripts/project-skill-extension.mjs inspect --skill setup-pre-commit --json` from the Project root. When it returns `active`, read the returned `path` and apply it as additive Project instructions. When it returns `inactive`, continue with Core only. When it returns `blocked`, stop and report its diagnostic.
+
+Project extensions may specialize Project details, but cannot weaken Core user gates, safety, ownership, or validation. A contradiction blocks and requires an Explicit fork.
+<!-- project-extension:protocol-v1:end -->
+
 # Setup Pre-Commit Hooks (native git, zero-dep)
 
 ## What This Sets Up

package/.claude/skills/setup-workflow/SKILL.md

@@ -4,6 +4,14 @@ description: "Scaffolds the project layer the portable workflow skills assume
 disable-model-invocation: true
 ---
 
+<!-- project-extension:protocol-v1:start -->
+## Project extension
+
+Before applying this Core skill, run `node scripts/project-skill-extension.mjs inspect --skill setup-workflow --json` from the Project root. When it returns `active`, read the returned `path` and apply it as additive Project instructions. When it returns `inactive`, continue with Core only. When it returns `blocked`, stop and report its diagnostic.
+
+Project extensions may specialize Project details, but cannot weaken Core user gates, safety, ownership, or validation. A contradiction blocks and requires an Explicit fork.
+<!-- project-extension:protocol-v1:end -->
+
 # Setup Workflow
 
 Scaffold the **project layer** the portable workflow skills (`to-prd`, `to-issues`, `triage`, `spec-self-critique`, `retro`, `wrapup`, …) read at runtime. The generic skills ship the *how*; this skill writes the project-specific *what* into the consumer repo, where `retro`/`wrapup` then grow it over time.
@@ -48,6 +56,28 @@ Every project-layer file this skill (or `npx init`) creates begins with **one se
 - **CLAUDE.md / AGENTS.md carry no sentinel** (they are not ours) → reconcile **per section** via the block headers `## Workflow` / `## Agent skills` / `## Prod`: add a missing block, never overwrite an existing one or surrounding user content.
 - **Never overwrite filled content.** A re-run only fills what is missing/stub. End with a report: `<file>: created · filled · skipped (already filled / legacy / not-applicable)`.
 
+## Universal Project skill extensions
+
+Every shipped skill can consume an additive Project extension at
+`docs/agents/skills/<skill>.md`. A newly created extension starts with this
+identity and schema marker (after the optional setup-workflow sentinel):
+
+```md
+<!-- agent-workflow-kit: project-extension/v1; skill=<skill> -->
+```
+
+The marker's `<skill>` must match the filename and a canonical or locally
+registered skill identity. Existing non-empty files without a marker remain
+supported as legacy v0 and are never rewritten merely to add the marker.
+Setup and update preserve every extension byte-for-byte unless a future,
+declared schema migration explicitly includes it.
+
+Use an extension for Project language, commands, policy, and capability data
+that the Core skill already knows how to apply. It is additive and cannot
+weaken Core user gates, safety, ownership, or validation. Changes to parsing,
+migration, evaluation, or other executable Core semantics require an
+Explicit fork with a separate identity and update line.
+
 ## Process
 
 ### 1. Explore

package/.claude/skills/setup-workflow/orchestrate-wave-seed.md

@@ -1,3 +1,4 @@
+<!-- agent-workflow-kit: project-extension/v1; skill=orchestrate-wave -->
 # Project layer — orchestrate-wave
 
 The generic `orchestrate-wave` skill ships the full wave-landing **mechanics**

package/.claude/skills/setup-workflow/spec-self-critique-seed.md

@@ -1,3 +1,4 @@
+<!-- agent-workflow-kit: project-extension/v1; skill=spec-self-critique -->
 # Project layer — spec-self-critique
 
 The generic `spec-self-critique` skill ships the 12-point checklist (the check *intents* + the structure). This file is the **project layer**: it enriches each point with project-specific incidents, grep patterns, conventions, and extra sub-checks. The skill reads it at runtime; with this file present it runs the full pass instead of warning that the layer is absent.

package/.claude/skills/spec-self-critique/SKILL.md

@@ -3,6 +3,14 @@ name: spec-self-critique
 description: "Use AFTER writing or editing a spec (a `SPEC.md`/`PLAN.md` or any spec/design doc), BEFORE asking the user to review — runs a 12-point structural Self-Critique checklist, fixes issues inline, and emits a visible summary. Enriches each check from a project layer if one is present. Triggers right after a spec has been written. NOT for reviewing finished code/diffs (code-review) — this pass runs on the spec text itself."
 ---
 
+<!-- project-extension:protocol-v1:start -->
+## Project extension
+
+Before applying this Core skill, run `node scripts/project-skill-extension.mjs inspect --skill spec-self-critique --json` from the Project root. When it returns `active`, read the returned `path` and apply it as additive Project instructions. When it returns `inactive`, continue with Core only. When it returns `blocked`, stop and report its diagnostic.
+
+Project extensions may specialize Project details, but cannot weaken Core user gates, safety, ownership, or validation. A contradiction blocks and requires an Explicit fork.
+<!-- project-extension:protocol-v1:end -->
+
 # Spec Self-Critique
 
 A portable, structural self-review pass over a freshly written spec/plan. The **generic 12-point skeleton** below ships as-is; a **project layer** (if present) enriches each point with project-specific incidents, grep patterns, conventions, and extra sub-checks.

package/.claude/skills/tdd/SKILL.md

@@ -3,6 +3,14 @@ name: tdd
 description: Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
 ---
 
+<!-- project-extension:protocol-v1:start -->
+## Project extension
+
+Before applying this Core skill, run `node scripts/project-skill-extension.mjs inspect --skill tdd --json` from the Project root. When it returns `active`, read the returned `path` and apply it as additive Project instructions. When it returns `inactive`, continue with Core only. When it returns `blocked`, stop and report its diagnostic.
+
+Project extensions may specialize Project details, but cannot weaken Core user gates, safety, ownership, or validation. A contradiction blocks and requires an Explicit fork.
+<!-- project-extension:protocol-v1:end -->
+
 # Test-Driven Development
 
 ## Philosophy

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

@@ -3,6 +3,14 @@ name: to-issues
 description: Break a Feature or Program plan, spec, or PRD into independently-grabbable issues on the project issue tracker. This is the single public Planning facade: explicit Feature identity uses tracer-bullet decomposition; explicit Program identity delegates to the internal graph engine.
 ---
 
+<!-- project-extension:protocol-v1:start -->
+## Project extension
+
+Before applying this Core skill, run `node scripts/project-skill-extension.mjs inspect --skill to-issues --json` from the Project root. When it returns `active`, read the returned `path` and apply it as additive Project instructions. When it returns `inactive`, continue with Core only. When it returns `blocked`, stop and report its diagnostic.
+
+Project extensions may specialize Project details, but cannot weaken Core user gates, safety, ownership, or validation. A contradiction blocks and requires an Explicit fork.
+<!-- project-extension:protocol-v1:end -->
+
 # To Issues
 
 > **Skill identity (don't get confused):** the folder `to-issues` + invocation `/to-issues` map to Matt Pocock's upstream skill **`to-tickets`**. Upstream merged `to-issues` + the short-lived `to-plan` into `to-tickets` (v1.1.0); we deliberately keep the folder name `to-issues` (invocation stability, and issues are this workflow's vocabulary). Content remains our fork, compared against upstream `to-tickets` @ `d574778`. Provenance/rename ledger: `docs/agents/provenance.md` (§Re-Sync-Log), at the project root.

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

@@ -4,6 +4,14 @@ disable-model-invocation: true
 description: "Turn a locked plan (PLAN.md in the worktree, conversation context, or an externally-authored spec) into a Draft-PRD issue on the project board, then run spec-self-critique. Use after a grill (grill-me / grill-with-docs / their -codex variants) when you want to publish the PRD. Three modes — create fresh, reuse an existing cluster/Wave-less issue, or auto-detect a Program-PRD from a plan's Wellenplan chapter. Does NOT decompose into slices (that is to-issues) and does NOT set type:cluster / Wave (that is to-issues promotion)."
 ---
 
+<!-- project-extension:protocol-v1:start -->
+## Project extension
+
+Before applying this Core skill, run `node scripts/project-skill-extension.mjs inspect --skill to-prd --json` from the Project root. When it returns `active`, read the returned `path` and apply it as additive Project instructions. When it returns `inactive`, continue with Core only. When it returns `blocked`, stop and report its diagnostic.
+
+Project extensions may specialize Project details, but cannot weaken Core user gates, safety, ownership, or validation. A contradiction blocks and requires an Explicit fork.
+<!-- project-extension:protocol-v1:end -->
+
 # to-prd — Draft PRD to the Board
 
 > **Skill identity (don't get confused):** the folder `to-prd` + invocation `/to-prd` map to Matt Pocock's upstream skill **`to-spec`**. Upstream renamed `to-prd` → `to-spec` (v1.1.0); we deliberately keep the folder name `to-prd` (invocation stability, and PRD is this workflow's vocabulary). Content remains our fork, compared against upstream `to-spec` @ `d574778`. Provenance/rename ledger: `docs/agents/provenance.md` (§Re-Sync-Log), at the project root.

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

@@ -4,6 +4,14 @@ disable-model-invocation: true
 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."
 ---
 
+<!-- project-extension:protocol-v1:start -->
+## Project extension
+
+Before applying this Core skill, run `node scripts/project-skill-extension.mjs inspect --skill to-waves --json` from the Project root. When it returns `active`, read the returned `path` and apply it as additive Project instructions. When it returns `inactive`, continue with Core only. When it returns `blocked`, stop and report its diagnostic.
+
+Project extensions may specialize Project details, but cannot weaken Core user gates, safety, ownership, or validation. A contradiction blocks and requires an Explicit fork.
+<!-- project-extension:protocol-v1:end -->
+
 # to-waves — Internal Program graph engine
 
 This skill is an **Internal Program graph engine**, selected by `to-issues` only

package/.claude/skills/triage/SKILL.md

@@ -4,6 +4,14 @@ disable-model-invocation: true
 description: Triage issues through the project board workflow. Use when user wants to triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
 ---
 
+<!-- project-extension:protocol-v1:start -->
+## Project extension
+
+Before applying this Core skill, run `node scripts/project-skill-extension.mjs inspect --skill triage --json` from the Project root. When it returns `active`, read the returned `path` and apply it as additive Project instructions. When it returns `inactive`, continue with Core only. When it returns `blocked`, stop and report its diagnostic.
+
+Project extensions may specialize Project details, but cannot weaken Core user gates, safety, ownership, or validation. A contradiction blocks and requires an Explicit fork.
+<!-- project-extension:protocol-v1:end -->
+
 # Triage
 
 Move issues on the project issue tracker through the board-driven workflow.

package/.claude/skills/verify-spike/SKILL.md

@@ -3,6 +3,14 @@ name: verify-spike
 description: Answer a single yes/no factual question about reality with a minimal throwaway, read-only harness and output-proof. Use when a plan, ADR, or implementation hinges on an empirically-checkable fact — does a library API exist / behave this way on this version, does the runtime / DB / platform actually have this capability, does an external assumption hold — and you need a proven verdict before locking the decision. NOT for design exploration (prototype), bug root-cause (diagnose), or building a feature (tdd).
 ---
 
+<!-- project-extension:protocol-v1:start -->
+## Project extension
+
+Before applying this Core skill, run `node scripts/project-skill-extension.mjs inspect --skill verify-spike --json` from the Project root. When it returns `active`, read the returned `path` and apply it as additive Project instructions. When it returns `inactive`, continue with Core only. When it returns `blocked`, stop and report its diagnostic.
+
+Project extensions may specialize Project details, but cannot weaken Core user gates, safety, ownership, or validation. A contradiction blocks and requires an Explicit fork.
+<!-- project-extension:protocol-v1:end -->
+
 # Verify Spike
 
 A verify-spike is **throwaway, read-only code that proves a yes/no fact about reality.** The question is binary; the spike makes the answer empirical instead of assumed.

package/.claude/skills/wayfinder/SKILL.md

@@ -4,6 +4,14 @@ description: Plan a huge chunk of work — more than one agent session can hold
 disable-model-invocation: true
 ---
 
+<!-- project-extension:protocol-v1:start -->
+## Project extension
+
+Before applying this Core skill, run `node scripts/project-skill-extension.mjs inspect --skill wayfinder --json` from the Project root. When it returns `active`, read the returned `path` and apply it as additive Project instructions. When it returns `inactive`, continue with Core only. When it returns `blocked`, stop and report its diagnostic.
+
+Project extensions may specialize Project details, but cannot weaken Core user gates, safety, ownership, or validation. A contradiction blocks and requires an Explicit fork.
+<!-- project-extension:protocol-v1:end -->
+
 A loose idea has arrived — too big for one agent session, and wrapped in fog: the way from here to the **destination** isn't visible yet. Wayfinding is about finding that way, not charging at the destination. This skill charts the way as a **shared map** on the repo's issue tracker, then works its tickets one at a time until the route is clear.
 
 The destination varies per effort, and naming it is the first act of charting — it shapes every ticket. It might be a spec to hand off and iterate on, a decision to lock before planning starts, or a change made in place like a data-structure migration. The map is domain-agnostic — engineering work, course content, whatever fits the shape.

package/.claude/skills/wrapup/SKILL.md

@@ -14,6 +14,14 @@ description: >-
   push, a conflicting PR, or red (FAILURE) checks.
 ---
 
+<!-- project-extension:protocol-v1:start -->
+## Project extension
+
+Before applying this Core skill, run `node scripts/project-skill-extension.mjs inspect --skill wrapup --json` from the Project root. When it returns `active`, read the returned `path` and apply it as additive Project instructions. When it returns `inactive`, continue with Core only. When it returns `blocked`, stop and report its diagnostic.
+
+Project extensions may specialize Project details, but cannot weaken Core user gates, safety, ownership, or validation. A contradiction blocks and requires an Explicit fork.
+<!-- project-extension:protocol-v1:end -->
+
 # wrapup — land PR & tear down worktree
 
 Trigger: user types `/wrapup` (optionally with a PR number). **Manual only** — `disable-model-invocation: true`, no hook, no auto-invoke.

package/.claude/skills/write-a-skill/SKILL.md

@@ -3,6 +3,14 @@ name: write-a-skill
 description: Create, write, edit, and improve agent skills — the vocabulary and principles that make a skill predictable (invocation, information hierarchy, progressive disclosure, leading words, pruning, failure modes). Use when the user wants to create, write, edit, refactor, or improve a skill.
 ---
 
+<!-- project-extension:protocol-v1:start -->
+## Project extension
+
+Before applying this Core skill, run `node scripts/project-skill-extension.mjs inspect --skill write-a-skill --json` from the Project root. When it returns `active`, read the returned `path` and apply it as additive Project instructions. When it returns `inactive`, continue with Core only. When it returns `blocked`, stop and report its diagnostic.
+
+Project extensions may specialize Project details, but cannot weaken Core user gates, safety, ownership, or validation. A contradiction blocks and requires an Explicit fork.
+<!-- project-extension:protocol-v1:end -->
+
 # Writing Skills
 
 > **Skill identity (don't get confused):** the folder `write-a-skill` + invocation `/write-a-skill` map to Matt Pocock's upstream skill **`writing-great-skills`**. Upstream replaced the old process-/template-based `write-a-skill` with this vocabulary/principles reference and switched it to **user-invoked** (`disable-model-invocation: true`). We keep the folder name `write-a-skill` (invocation stability) **and** deliberately keep it **model-invoked** (auto-fires on "create/write a skill" + `/write-a-skill`, as referenced in CLAUDE.md `## Workflow`). Content = upstream `writing-great-skills` @ `7a83a3a`, locally adapted. Provenance/rename ledger: `docs/agents/provenance.md` (§Re-Sync-Log), at the project root.

package/README.md

@@ -331,13 +331,16 @@ npx github:iKon85/agent-workflow-kit uninstall   # remove kit-installed files
 - a file you **did** edit is kept — the incoming version is backed up with a
   timestamp and a diff is printed, never silently overwritten;
 - a file you intentionally fork can be detached with
-  `npx github:iKon85/agent-workflow-kit own <path>` and returned to kit ownership
+  `npx github:iKon85/agent-workflow-kit own <path> --as=explicit-fork`, retained
+  temporarily with `--as=contribution-bridge`, and returned to kit ownership
   with `npx github:iKon85/agent-workflow-kit disown <path>`; owned files are
   skipped by updates even after the package stops shipping them;
 - a file removed upstream is offered for deletion (a hook still referenced by your
   `settings.json` is kept regardless);
-- a new kit path that already exists locally is reported as a collision: choose
-  either to keep the existing file as consumer-owned or replace it with kit bytes;
+- a new Kit path that already exists locally is an `ambiguous-collision` until
+  an interactive or automated caller explicitly classifies it as a Project
+  extension, Contribution Bridge, Explicit fork, or clean Core; `--yes` never
+  chooses that interpretation and never overwrites the path;
 - new skills without a local collision are added.
 
 Ownership survives repeated `init`, including `init --force`: consumer-owned
@@ -354,7 +357,24 @@ Containment and file type are revalidated when read.
 Ownership commands are designed for a single-user CLI workflow and are not
 concurrency-safe. Do not run manifest-mutating commands concurrently. Flags:
 `--force` (overwrite pre-existing untracked files on `init`), `--yes` / `-y`
-(accept non-interactive update decisions).
+(confirm only already-classified safe update actions), and
+`--as=contribution-bridge|explicit-fork` for `own`.
+
+### Project extensions versus forks
+
+Every shipped skill probes the optional consumer-owned
+`docs/agents/skills/<skill>.md` after loading its canonical Core. New
+extensions declare
+`<!-- agent-workflow-kit: project-extension/v1; skill=<skill> -->`; existing
+non-empty unmarked files remain supported as legacy v0. Claude and Codex use
+the same extension path and fail closed on an unknown schema or mismatched
+identity.
+
+Use an extension for Project-specific language, commands, policy, or
+capability data. It augments Core and survives setup and updates byte-for-byte;
+it cannot weaken Core gates or replace executable semantics. If you need to
+change parsing, migration, evaluation, or other executable behavior, create an
+Explicit fork with its own identity and update line instead.
 
 ## Upgrade notes
 
@@ -387,6 +407,100 @@ the old way. Decision record:
 
 ## Release notes
 
+### 0.35.0
+
+- added: `scripts/project-skill-extension.mjs`
+- added: `src/lib/ownershipClassifier.mjs`
+- added: `src/lib/projectSkillExtension.mjs`
+- added: `src/lib/skillRegistry.mjs`
+- added: `src/lib/updateDecisions.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/census-update/SKILL.md`
+- changed: `.agents/skills/code-review/SKILL.md`
+- changed: `.agents/skills/codebase-design/SKILL.md`
+- changed: `.agents/skills/codex-adapter-sync/SKILL.md`
+- changed: `.agents/skills/decision-gate/SKILL.md`
+- changed: `.agents/skills/diagnose/SKILL.md`
+- changed: `.agents/skills/domain-modeling/SKILL.md`
+- changed: `.agents/skills/git-worktree-recover/SKILL.md`
+- changed: `.agents/skills/grill-me/SKILL.md`
+- changed: `.agents/skills/grill-with-docs/SKILL.md`
+- changed: `.agents/skills/implement/SKILL.md`
+- changed: `.agents/skills/improve-codebase-architecture/SKILL.md`
+- changed: `.agents/skills/kit-release/SKILL.md`
+- changed: `.agents/skills/kit-update/SKILL.md`
+- changed: `.agents/skills/local-ci/SKILL.md`
+- changed: `.agents/skills/memory-lifecycle/SKILL.md`
+- changed: `.agents/skills/orchestrate-wave/SKILL.md`
+- changed: `.agents/skills/project-release/SKILL.md`
+- changed: `.agents/skills/prototype/SKILL.md`
+- changed: `.agents/skills/research/SKILL.md`
+- changed: `.agents/skills/resolving-merge-conflicts/SKILL.md`
+- changed: `.agents/skills/retro/SKILL.md`
+- changed: `.agents/skills/scale-check/SKILL.md`
+- changed: `.agents/skills/security-audit/SKILL.md`
+- changed: `.agents/skills/setup-workflow/SKILL.md`
+- changed: `.agents/skills/setup-workflow/orchestrate-wave-seed.md`
+- changed: `.agents/skills/setup-workflow/spec-self-critique-seed.md`
+- changed: `.agents/skills/spec-self-critique/SKILL.md`
+- changed: `.agents/skills/tdd/SKILL.md`
+- changed: `.agents/skills/to-issues/SKILL.md`
+- changed: `.agents/skills/to-prd/SKILL.md`
+- changed: `.agents/skills/to-waves/SKILL.md`
+- changed: `.agents/skills/triage/SKILL.md`
+- changed: `.agents/skills/verify-spike/SKILL.md`
+- changed: `.agents/skills/wayfinder/SKILL.md`
+- changed: `.agents/skills/wrapup/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/census-update/SKILL.md`
+- changed: `.claude/skills/code-review/SKILL.md`
+- changed: `.claude/skills/codebase-design/SKILL.md`
+- changed: `.claude/skills/codex-build/SKILL.md`
+- changed: `.claude/skills/codex-review/SKILL.md`
+- changed: `.claude/skills/decision-gate/SKILL.md`
+- changed: `.claude/skills/diagnose/SKILL.md`
+- changed: `.claude/skills/domain-modeling/SKILL.md`
+- changed: `.claude/skills/git-guardrails-claude-code/SKILL.md`
+- changed: `.claude/skills/git-worktree-recover/SKILL.md`
+- changed: `.claude/skills/grill-me-codex/SKILL.md`
+- changed: `.claude/skills/grill-me/SKILL.md`
+- changed: `.claude/skills/grill-with-docs-codex/SKILL.md`
+- changed: `.claude/skills/grill-with-docs/SKILL.md`
+- changed: `.claude/skills/implement/SKILL.md`
+- changed: `.claude/skills/improve-codebase-architecture/SKILL.md`
+- changed: `.claude/skills/kit-release/SKILL.md`
+- changed: `.claude/skills/kit-update/SKILL.md`
+- changed: `.claude/skills/local-ci/SKILL.md`
+- changed: `.claude/skills/memory-lifecycle/SKILL.md`
+- changed: `.claude/skills/orchestrate-wave/SKILL.md`
+- changed: `.claude/skills/project-release/SKILL.md`
+- changed: `.claude/skills/prototype/SKILL.md`
+- changed: `.claude/skills/research/SKILL.md`
+- changed: `.claude/skills/resolving-merge-conflicts/SKILL.md`
+- changed: `.claude/skills/retro/SKILL.md`
+- changed: `.claude/skills/scale-check/SKILL.md`
+- changed: `.claude/skills/security-audit/SKILL.md`
+- changed: `.claude/skills/setup-pre-commit/SKILL.md`
+- changed: `.claude/skills/setup-workflow/SKILL.md`
+- changed: `.claude/skills/setup-workflow/orchestrate-wave-seed.md`
+- changed: `.claude/skills/setup-workflow/spec-self-critique-seed.md`
+- changed: `.claude/skills/spec-self-critique/SKILL.md`
+- changed: `.claude/skills/tdd/SKILL.md`
+- changed: `.claude/skills/to-issues/SKILL.md`
+- changed: `.claude/skills/to-prd/SKILL.md`
+- changed: `.claude/skills/to-waves/SKILL.md`
+- changed: `.claude/skills/triage/SKILL.md`
+- changed: `.claude/skills/verify-spike/SKILL.md`
+- changed: `.claude/skills/wayfinder/SKILL.md`
+- changed: `.claude/skills/wrapup/SKILL.md`
+- changed: `.claude/skills/write-a-skill/SKILL.md`
+- changed: `scripts/readiness.mjs`
+- changed: `src/lib/manifest.mjs`
+
 ### 0.34.6
 
 - changed: `.agents/skills/kit-release/SKILL.md`