ship-feature
Ship Feature
Run a closed loop: discover → plan → implement → prove → review → repair. The main agent is the flight controller: it owns decisions, repository safety, evidence, PR state, and the loop. Subagents receive bounded roles; their confidence never substitutes for verification.
Use these default profiles:
| Role | Model | Effort |
|---|---|---|
| Planner | GPT-5.6 Sol | Medium |
| Implementer | GPT-5.6 Luna | High |
| Reviewer | GPT-5.6 Sol | Medium |
Treat profile names as configured model aliases. Ask the user before substituting a model, changing effort, or adding a role. A fresh reviewer is another iteration of the existing Reviewer role, not a new role. Never emulate an independent Reviewer in the main context.
Before dispatching a role, read the Common contract and that role's contract in ROLE-CONTRACTS.md; include both in the subagent prompt.
1. Establish the flight plan
Read the feature request, repository instructions, relevant source, tests, architecture, issue context, and delivery conventions. Preflight: