monobun

Use after builder-workflow checkup passes for a plan phase and before git-pr-workflow, to sync docs/AGENTS/README/skills with code per the plan Documentation before PR list. Not during builder implement.

Use when an approved plan phase should be built (code/config only) via subagents through checkup and review, stopping before documentation-sync and git-pr. Use as step 2 of initiative-workflow.

Use when multi-step or cross-package work needs a written plan before coding, when the user asks for phases/PRs/impact map, or when producing `.cursor/plans/*.plan.md` with code and doc-before-PR sections. Use as step 1 of initiative-workflow.

Monobun ship path — bun overall, working tree, branch gate, staged diff, context-aware conventional commit, precommit, push, and PR body from .github/pull_request_template.md (not fill-only). Use when the user asks to commit, push, open a PR, or finish a branch.

Use when starting a multi-phase feature and need the ordered skill pipeline from product context through plan, build, documentation sync, and PR. Use when unsure which skill runs when or how much context to pass at each step.

Bun entry scripts under tools/scripts/<area>/ with subcommands, node:util parseArgs, Ink step progress (Static + spinner), renderAndExit, and quiet mode without duplicate logic. Use when adding or refactoring repo CLI scripts, local/dev/prod commands, postinstall hooks, or anything mirroring tools/scripts/local/.