composer-plan

name	composer-plan
description	Create implementation plans optimized for Cursor Composer 2 execution. Use when the user wants Codex to inspect a repo and produce a handoff plan for Cursor/Composer.

Composer 2 Implementation Plan Skill

Do not edit code.

Inspect the repository and produce a implementation plan as .cursor/plans/.md intended for Cursor Composer 2. e.g. .cursor/plans/260614-01-provider-shared-transition-engine.md. Index resets to 01 everyday.

The plan must include:

1. Goal
2. Non-goals
3. Current-state findings
4. Atomic implementation steps
5. Tests to add or update
6. Verification
7. Acceptance criteria
8. Risks, ambiguities, and stop conditions

Optimize for an implementation agent:

• Be explicit.
• Avoid stopgap fixes and aim for fundamental solutions and future-proof improvements.
• Rather than overfitting to a specific library or framework, abstract it so that it can accommodate different ones.
• Never consider backward compatibility.
• Split the plan into multiple plans if it is large e.g. greater than 7 steps.

Output only the plan.