maipai

Direct one or more coder sessions to completion without coding yourself - assign lanes, write their work orders, run the ready handshake, answer questions, classify and clear blockers, verify completion reports against acceptance, and hand off cleanly when a session runs out of context. Use when Jesse says to manage, direct, coordinate, or run other sessions, or when a session is on Fable (which always holds this role).

File a bug, a feature request, or an idea as a GitHub issue in the current getmaipai repo, fast and without duplicates - search open issues first, comment on a match, otherwise file with the org's plain-language template and the right label. Use when Jesse or a session says "file an issue", "log a bug", "feature request", "it would be nice if", "add this to the wishlist", or notices a defect mid-task that is not being fixed now.

Scaffold a new getmaipai/catalog package (plugin, app, companion, integration, model, wakeword, voice, or theme) with a conforming manifest and the bronze-tier definition of done. Use when starting a new package, or when a legacy feature's review verdict (PACKAGES.md) is "rebuild" or "redesign" and it is time to build it.

Cut a MaiPai release - checks, clean-clone build, changelog from commits, screenshot regeneration, docs drift check, semver tag, GitHub release. Use when Jesse says release, cut a release, or ship a version.

Verify a getmaipai repo is correctly pinned to @maipai/standards and its check.sh core passes. Use when setting up a new repo's check.sh, auditing which std-vX.Y.Z a repo targets, or when the release skill needs to confirm a repo is current before cutting a release.

Refresh the MaiPai Build Status dashboard (an Artifact) from every repo's docs/BACKLOG.md and open GitHub issue counts. Use whenever a docs/BACKLOG.md changes, at latest before a session ends, or when Jesse asks for the dashboard to be brought current.

Refresh a MaiPai repo's README and user docs with the latest shipped features and privacy-safe generated screenshots. Use when features shipped since the last docs update or Jesse asks to update docs, README, or screenshots.

The MaiPai verification contract - what "verified" means before any commit in an org repo. Use before committing any nontrivial change, or when Jesse asks whether something was verified.

Run the two-pass AI review over a batch of generated screenshots (session open-and-confirm, then the pipeline's declared-expectation check) before they are used anywhere. Use after regenerating screenshots for the hub, robot, Go, or a catalog package, or when Jesse asks whether screenshots are actually right.