konjo-ship

name	konjo-ship
description	Konjo sprint completion checklist and session handoff template for kairu. Use when closing out a sprint or ending a work session.
user-invocable	true

Konjo Ship — kairu

Sprint Completion Checklist

A sprint is not complete until every one of these is true:

[ ] All success criteria met
[ ] All tests pass — `python -m pytest` green, zero failures
[ ] `ruff check` and `ruff format --check` clean
[ ] CHANGELOG.md updated — human-readable, what changed and why it matters
[ ] PLAN.md updated — completed items checked, next items identified
[ ] README.md reflects current state — no stale claims, no missing capabilities
[ ] Zero debug artifacts, dead code, or leftover scaffolding
[ ] git add && git commit -m "type(scope): description" && git push

A sprint that is "basically done" is not done. Ship clean or don't ship.

Execute Checklist

ᨀᨚᨐᨚ — Build the ship. Make it seaworthy.

PLAN    — write the implementation steps before touching code
BUILD   — one step at a time, logical commits
TEST    — run existing tests, write new ones, fix failures immediately
REVIEW  — re-read everything just written — is it beautiful? is it lean? is it Konjo?
ITERATE — when something breaks, go back to the source — no papering over
SHIP    — all tests pass, docs updated, changelog written, then push

Session Handoff Template

SHIPPED      [what was completed this session]
TESTS        [passing / failing / count]
PUSHED       [commit hash or "not pushed — reason"]
NEXT SESSION [the exact next task — not "continue the work"]
DISCOVERIES  [papers, repos, techniques found this session worth revisiting]
HEALTH       [Green / Yellow / Red — one line]

Every session is a step toward something larger. Make the handoff count. Mahiberawi Nuro — we build together. Leave the work ready for the next person.