Turn an analyzed request into an implementation-ready plan, optionally backed by a GitHub issue. Use when the user invokes $plan or continues the APEX workflow.
---
name: plan
description: Turn an analyzed request into an implementation-ready plan, optionally backed by a GitHub issue. Use when the user invokes $plan or continues the APEX workflow.
argument-hint: "<analysis or request>"
---
Turn the current analysis into one implementation-ready plan.
Include the problem, desired behavior, scope, out of scope, implementation decisions, measurable acceptance criteria, and verification requirements. Prefer behavioral requirements over file paths or code snippets.
Return the plan directly. Create a durable GitHub issue when the user requests it, repository rules require it, or the plan is large:
- three or more independent implementation units
- multiple subsystems or owners
- a migration, deployment, or external coordination
- unlikely to finish in one focused session
When an issue is needed, follow the repository's GitHub attribution rules, create or update it in the authorized scope, read it back, and return its URL with the plan. GitHub being down must not block a focused plan that does not need an issue.
Do not implement.