prospec: Skill for Claude Code

Release Skill

Cut a new prospec release from main: bump the version strings, create the tag, and publish GitHub release notes in the house format. Publishing the release (published event) triggers .github/workflows/release.yml, which compiles the multi-platform standalone binaries and attaches them as compressed assets — so this skill's job is the version bump + notes, not the build.

Language

The release notes, commit message, and everything this skill writes are in English — a release is trust-zone / public-facing technical output, exempt from the Traditional Chinese change-artifact rule (see prospec/CONSTITUTION.md → Language Policy, mirrored in AGENTS.md). Talk to the user in their language; write the artifacts in English.

Preconditions — do not release until all hold

1. All PRs for this version are merged to main and main is checked out with a clean tree (git status). gh pr list --state open --base main is empty. A release is cut from main, never a feature branch.

2. Each change is archived (/prospec-archive) — REQs graduated, Knowledge synced, summary written. prospec status reports no in-progress changes. The release notes' Dogfood section reports this; it must already be true.

3. Counts are already synced. pnpm counts runs as the last step of each feature commit, not here — READMEs / index.md / module READMEs already carry the right test/skill counts. Do not run pnpm counts during the bump. (See memory: counts are generated by sync-counts.ts.)

4. Green locally with the current CI/release gates. Run the coverage suite once, then reuse its explicit JSON report for the factual-count check so the suite is not run twice:

   pnpm test:coverage
   pnpm typecheck
   pnpm lint
   pnpm counts:check --from vitest-report.json
   pnpm agents:check
   pnpm knowledge:check
   prospec check --strict
   pnpm bundle
   

   coverage/ and vitest-report.json on disk may be stale; only figures from this invocation are release evidence. knowledge:check may honestly skip when the release-only diff touches no module-owned source — report that result rather than manufacturing work. Capture the numbers for the "Quality & tests" section. Read prospec check WARNs by type, not as one bucket:

   • knowledge-health (stale module README) — almost always a prior change's archive that changed a module's source but never touched its README (drift compares git commit times). Fix it before releasing: sync + commit that module README so the notes can honestly claim a green check. Then confirm the fix didn't tip knowledge-size over the L2 per-module budget (this project overrides it to 2000 tokens in .prospec.yaml; the shipped default is 1000) — if it did, trim the README back under budget (net-neutral) rather than accept a new WARN.
   • knowledge-size budget WARN that pre-exists and is deliberate (the SC-002 signal) may be reported as such, mirroring how 0.5.2 framed it — do not thrash the README to chase it away.