/ship-cycle

Turns improvement intent into shipped versions, deterministically: intent → issues → milestones = versions → tagged release. Direct-call only. Given a backlog (pasted notes, a /vibesubin sweep report, or a named scope), this skill writes a well-specified bilingual issue set, clusters items into semver milestones, dispatches the implementation to the correct vibesubin specialist, and — when a milestone closes — runs the full release pipeline end-to-end: changelog aggregation, manifest bump, annotated tag, GitHub release, audit trail. No interpretation, no flourish — the milestone state is the release state.

What this skill owns vs. hands off

Owns:

• Issue specification — titles, bodies, labels, dependency links, language.
• Milestone clustering — semver classification, cluster heuristics, cap enforcement.
• Release pipeline — preflight checks, changelog aggregation, version bump, annotated tag, gh release create, verification.
• Audit trail — close-comments on issues, milestone closure, release ↔ issue linkage.

Hands off:

• Actual code changes — the fix itself is always another skill's job (refactor-verify, audit-security, etc.).
• Release-note prose — write-for-ai writes the user-facing narrative when the operator wants polish; this skill produces the functional-only scaffold.
• CI wiring — setup-ci owns workflow files.