plan turns the analyzed request into the contract used by downstream skills.
Output
The plan records the problem, desired behavior, scope, exclusions, implementation decisions, acceptance criteria, and verification requirements. A focused plan is returned directly. An issue is created when requested, required by repository rules, or needed for work spanning multiple units, systems, or sessions. When an issue is created, the agent reads it back and returns its URL.
Boundary
This stage does not implement the plan. GitHub is not required for a focused plan that does not need an issue.
Terminal
/plan use the current analysis