Some blockers are neither a decision, a prototype, nor research — just
literal manual work (moving data, signing up for a service, provisioning
access) that must happen before discussion can move forward.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Tests whose assertion is recomputed the way the code computes it pass by
construction and give zero confidence. Add it as a peer of the existing
implementation-coupling anti-pattern: a Philosophy principle, a per-cycle
checklist gate, and a BAD/GOOD example pair in tests.md. Includes a patch
changeset.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Add `publish: npx changeset tag` to the release workflow and enable
tagging for private packages in the changesets config, so merging a
Version PR creates a git tag and GitHub release.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add changesets for tracking and versioning skill changes:
- package.json (private) + @changesets/cli and @changesets/changelog-github
- .changeset/config.json using the GitHub release-style changelog
- release workflow that opens a version PR on push to main (no npm publish)
- initial changeset recording recent skill updates
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
