Menu
Konjo sprint completion checklist and session handoff template for songscraper. Use when closing out a sprint or ending a work session.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Boot a Konjo session for songscraper. Produces a Session Brief, runs Discovery, identifies the next sprint. Use at the start of any work session or when invoked with /konjo.
Konjo Code Quality Framework — gate definitions, thresholds, tools, and enforcement points for songscraper. Auto-load when writing tests, reviewing code quality, refactoring, or when quality gate failures are mentioned. Applies the Three-Wall framework to prevent AI slop.
Retrofit the Konjo Quality Framework onto an existing repo that predates it. Use when asked to add konjo quality gates, improve code quality, audit an existing codebase, or run a quality sprint. Provides the step-by-step migration plan and triage protocol.
Full songscraper project context — architecture, the Crown Jewels formatter contract, standing rules for agents, and deployment shape. Auto-load when working on scraping, formatting, Google auth, or Cloud Run deployment.
Based on SOC occupation classification
| name | konjo-ship |
| description | Konjo sprint completion checklist and session handoff template for songscraper. Use when closing out a sprint or ending a work session. |
| user-invocable | true |
A sprint is not complete until every one of these is true:
[ ] All success criteria met
[ ] All tests pass — `npm test` green, zero failures (formatter regression included)
[ ] `npm run lint` clean
[ ] `npm audit` — zero high/critical advisories
[ ] README.md / DEPLOY.md reflect current state — no stale claims, no missing capabilities
[ ] Zero debug artifacts, dead code, or leftover scaffolding (no stray console.log spam)
[ ] No secrets committed — .env / creds.json / token.json / refresh tokens out of the tree
[ ] 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.
ᨀᨚᨐᨚ — 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, then push
When things break — apply 根性:
src/config.js.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 [UG markup changes, dependency updates 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.