/kosuke:plan
/kosuke:plan plans a change with you before anything is built. Use it for a big feature or one whose intent is still unclear. /kosuke:ship uses its last two stages for a migration or a data backfill.
Run it
Type /kosuke:plan and what you want to build, or $kosuke:plan in a Codex session.
What it does
- Questions. It asks you rounds of numbered questions, each with its recommended answer, until no decision is open. It looks facts up in the code itself first.
- Spec. It writes
ticket.md: why, what changes, what it reuses, the decisions, acceptance criteria a tester can check, the prototype and what QA needs. - Attack. One model attacks the spec, read-only, at the hardest level. When the workspace has another AI provider, that model comes from it, so another family checks the plan; with one provider, it is that provider's strongest model. The agent accepts each objection and changes the spec, or rejects it with evidence. An objection to one of your answers comes back to you as a question. At most three rounds.
- Plan. It writes
plan.md: one section per phase in build order, with its files, how to check it and the acceptance criteria it covers, then the objections still open.
What you get
ticket.md, objections.md and plan.md in the Artifacts tab. Send /kosuke:ship next to build it.