| name | sdlc-ship |
| description | Phase 7 of the SDLC, the final phase. Use this to prepare a release after review has passed. Triggers when review.md shows all criteria passing. Runs the mandatory security-scan gate, generates release notes in Ukrainian, and prepares (but does not auto-execute) the commit/tag/PR. A failing security scan blocks the ship and is surfaced to the user. |
Phase 7 — Ship (release, gated)
Preconditions
specs/<feature>/review.md shows all criteria PASS.
Process (order matters)
- Security gate (hard). Invoke
security-scan. If it reports findings above the
project's threshold, STOP, summarize findings, and ask the user how to proceed. Never
bypass silently.
- Generate release notes from the spec + tasks (Ukrainian prose, EN technical identifiers).
- Prepare the commit message and proposed tag. Show them to the user.
- Ask for explicit confirmation before any
git commit, git push, gh pr create,
or tag. These are side effects — they require a clear "yes" in chat.
- After shipping, persist a final memory record (feature shipped, version, date) and
run
/skills-audit if the bundle grew during the project.
Rules
- A failing security scan blocks the ship. No exceptions without explicit user override.
- Never push or open a PR without confirmation.
Exit
Update state (phase=ship, version). Persist. Say: "Shipped . SDLC complete for ."
Примітка (UK)
Фаза релізу обов'язково проходить шлюз безпеки (security-scan). Будь-який commit/push/PR —
лише після явного підтвердження користувача в чаті. Реліз-ноти пишемо українською.
