shipper-plan
Explores your codebase, asks clarifying questions, and writes a phased markdown plan to .shipper/open/.
e.g. “use shipper-plan to plan dark mode settings”
Agent skills
Every workflow the console uses is a plain agent skill installed in your repo. Invoke them directly from Claude Code, Cursor, or opencode — no console required.
On your first shipper run, skills are installed automatically into .claude/skills/, .cursor/skills/, or .opencode/skill/ depending on your agent.
shipper-build
Executes one phase per agent session until the plan is complete, then moves it to .shipper/done/.
e.g. “use shipper-build on .shipper/open/my-feature.md Phase 2”
shipper-spike
Small one-off feature: plan and build in a single agent session.
e.g. “use shipper-spike to add a copy button to the hero”
shipper-ship
Scaffolds a reviewable pull request from a completed plan — what changed, how to verify, and known risks. Creates the PR via gh.
e.g. “use shipper-ship on .shipper/done/my-feature.md”
shipper-bug
Evidence-first bug catalog and fix workflow. Reproduce before diagnosing, then drive the fix to proof in .shipper/bugs/.
e.g. “use shipper-bug to fix the login redirect loop”
Plans are committed markdown in .shipper/, so console users and direct-skill users work from the same files.