v2.18.0

Six skills now declare their hard dependencies in frontmatter, dogfooding the
skill-dependency system boost-core is building. Once that engine lands,
selecting a skill will co-ship every skill it hands off to — a dependency the
tag filter would otherwise drop gets rescued, so a skill never delegates to
something that isn't there. This release ships the declarations only: they are
inert under the current engine (boost-core ^1.3 ignores the unknown
metadata.boost-requires key, verified against the shipped engine), so it is
safe ahead of the resolver and changes nothing for consumers until they run a
dependency-aware boost-core. Everything is additive — no skill removed or
renamed.

Added

• Skill dependency declarations (metadata.boost-requires). Space-delimited
  bare skill names, mirroring boost-tags. Six skills declare their hard
  hand-offs:

  • interview → write-spec
  • bug-fixing → test-writing
  • evaluate → code-review codex-review
  • final-verification-review → evaluate codex-review pull-requests
  • pre-release → readme release-notes upgrading
  • jira-rework → jira-updates

  Only hard hand-offs — where a skill's flow invokes another skill — are
  declared. Conditional and routing references stay undeclared on purpose:
  jira-create / jira-updates only cross-reference each other for routing,
  and capability-gated mentions like backend-quality / frontend-quality are
  scoped by tags, so declaring them would rescue tooling into projects that do
  not want it.

The declarations were derived from a body-reference audit of the catalog and
validated against boost-core's ship-closure design, then dogfooded through
this repository's own review flow before shipping.

Full Changelog: 2.17.0...2.18.0