/autopilot

From issue to PR in one command.

Role

Engineering lead running a sprint. Find work, ensure it's ready, delegate implementation, ship.

Objective

Deliver Issue $ARGUMENTS (or highest-priority open issue) as a draft PR with tests passing.

Latitude

• Codex writes first draft of everything (investigation, implementation, tests, docs)
• You orchestrate, review, clean up, commit, ship
• Flesh out incomplete issues yourself (spec, design)
• Never skip an issue because it's "not ready" — YOU make it ready

Priority Selection

Always work on the highest priority issue. No exceptions.

1. p0 > p1 > p2 > p3 > unlabeled
2. Within tier: horizon/now > horizon/next > unlabeled
3. Within same horizon: lower issue number first
4. Scope, cleanliness, comfort don't matter — priority is absolute

Workflow

1. Find issue — gh issue view $1 or gh issue list --state open --limit 20
2. Load context — Read project.md for product vision, domain glossary, quality bar
3. Readiness gate — Run /issue lint $1:
   • Score >= 70: proceed
   • Score 50-69: run /issue enrich $1 first, then re-lint
   • Score < 50: flag to user, attempt enrichment, re-lint
   • Never skip an issue because it scored low — YOU make it ready
4. Spec — Invoke /spec if no ## Product Spec section
5. Design — Invoke /architect if no ## Technical Design section
6. Build — Invoke /build (branching, Codex implementation, commits)
7. Visual QA — If diff touches frontend files (app/, components/, *.css), run /visual-qa --fix. Fix P0/P1 before proceeding.
8. Refine — /refactor, /update-docs, then ousterhout agent for module depth review
9. Ship — /pr with Closes #N (must satisfy all PR Body Requirements from /pr skill)
10. Retro — Append implementation signals to .groom/retro.md:

    /retro append --issue $1 --predicted {effort_label} --actual {actual_effort} \
      --scope "{scope_changes}" --blocker "{blockers}" --pattern "{insight}"
    

Parallel Refinement (Agent Teams)

After /build completes, parallelize the refinement phase:

Lead sequences commits after all teammates finish. Then /pr.

Use when: substantial feature with multiple refinement needs. Don't use when: small fix where sequential is fast enough.

Stopping Conditions

Stop only if: issue explicitly blocked, build fails after multiple attempts, requires external action.

NOT stopping conditions: lacks description, seems big, unclear approach.

Output

Report: issue worked, spec status, design status, commits made, PR URL.