ship

Use when a feature plan has been verified and is ready for implementation — executes tasks with atomic commits

Use when you want to auto-run all remaining Ship steps for a feature without manual step-by-step invocation

Use when a feature has been brainstormed and needs a detailed implementation plan with tasks

Use when a brainstormed feature needs architectural decisions — presents 2-3 approaches for user to choose before planning

Use when a plan has been created and needs independent verification against codebase patterns before building

Use when beginning new feature work, adding functionality, or fixing a bug — runs intensive brainstorming to capture requirements before planning

Use when the user asks about Ship commands, workflow, or how to use the framework

Use when returning to continue work on an in-progress feature — picks up where you left off based on feature status

Use when checking feature progress or wanting to see what features exist and their current status

Use when a feature build is complete and needs verification against acceptance criteria and adversarial testing

Use when a feature has been verified and needs to be completed — creates PR, merges locally, or keeps branch

Execute implementation plan with atomic commits per task

Present 2-3 architectural approaches for user to choose before planning

Use when plan diverges from reality during build execution — provides 3 escalation levels for handling failures

Complete verified feature — create PR, merge, or keep branch

Use when making git commits during Ship feature builds — provides atomic commit format and conventions

Auto-run all remaining Ship steps for a feature end-to-end

Explain Ship commands, workflow, and framework usage

Create detailed implementation plan with ordered tasks

Verify plan against codebase patterns before building

Continue work on an in-progress feature from where you left off

Brainstorm and capture requirements for a new feature or bug fix

Show feature progress and status across all features

Use when implementing tasks that have test-based verify commands — provides RED-GREEN-REFACTOR cycle guidance

Verify completed build against acceptance criteria with code review

Use when plan diverges from reality during build execution — provides 3 escalation levels for handling failures

Use when making git commits during Ship feature builds — provides atomic commit format and conventions

Use when implementing tasks that have test-based verify commands — provides RED-GREEN-REFACTOR cycle guidance