plan

Write an implementation plan: how to build a spec, GitHub issues, Azure DevOps work items, or what the conversation agreed, worked out against the real code. One file, under .scratch/ (or an existing, gitignored .local/) unless the repo's instructions name a location: goal, acceptance criteria, decisions, cautious readings, checks, slices only for work bigger than one session, and numbered steps that each name their criteria, files and symbols, the test to write first, and the check that shows the step is done. Asks only about choices a user would notice: once before drafting, and again only when a review finding needs one. An independent subagent reviews the plan, up to 3 rounds. Changes no code. Usage: /swe:plan [target …] [context]. User-invoked only.

Compatibility

Tickets come through the skill swe:fetch-tickets, called by name, else a paste: GitHub needs gh or the public API; Azure DevOps a work-item MCP tool or az. The review runs in a subagent, or inline as separate passes on hosts without one. Hosts that ignore disable-model-invocation lose the user-only guarantee.