feature

Pin repo facts BEFORE a planning turn, so the planner transcribes checked facts instead of inferring them. Use when about to plan or design any change against an existing codebase — "plan X", "design Y", "write a spec for Z" — and especially before handing a spec to /codex:implement, whose gates test whether code passes, never whether a premise was true. Produces a grounding doc and stops before design. NOT for planning itself, and not for changes small enough to hold in one turn.

Write a mid-phase handoff when a session must stop before its phase's output exists — quota exhausted, end of day, the context safety rail in the user's CLAUDE.md, or the 55-minute idle wake-up firing. Use for "/feature:handoff", "write a handoff", or when the idle wake-up prompt says to. NOT at a phase end: a phase's output (problem.md, plan.md, the PR, verdict JSONs, the report) is its own record and needs no handoff.

Run the feature pipeline's planning phase: spawn the planner on a grounded problem.md, then interactively approve its decisions, open questions and risks before ship. Use after /feature:ground and before /feature:ship — "plan X", "run the planner", "review the plan's decisions". This is the feature pipeline's plan step, NOT Claude Code's built-in /plan (plan mode). NOT for grounding, not for shipping, and not for a change small enough to hold in one turn.

Find the biggest wastes of effort in a finished orchestration session and route each fix back into the workflow it came from. Run in a SEPARATE session, passing the finished session's name: "/feature:retro <session-name>". Reads that session's transcript as evidence, ranks wastes by real token cost, and proposes fixes to ground, the planner and ship. NOT in the session being analysed (a session grading itself inherits the blind spot that caused the waste), and not for a one-turn task with nothing to rank.

Run a written plan through the codex and UX lanes to a shipped feature — launch the workstreams, write and run the probes, verify staging, triage the local review, run the fix lanes, decide production. Use when a `plan.md` exists and has passed the path checker: "/feature:ship <plan.md>", "run this plan", "ship this plan". NOT for planning, and not for a change small enough to do in one turn — there the launch overhead is the whole cost.