Implementation Plan

Use this skill to draft an implementation plan for one issue or tightly scoped change. This skill writes the plan; it does not itself perform the implementation or reviewer passes during planning.

Planning Context

Before drafting, gather only context needed to make the plan executable:

• The issue body, acceptance criteria, linked parent roadmap, and blocking dependencies.
• Relevant repository conventions, ownership boundaries, architecture, tests, and validation commands.
• Existing behavior that must remain stable.
• Explicit user constraints around migrations, rollout, compatibility, deadlines, or merge authorization.

Ask a concise follow-up only when a missing decision would materially change implementation scope or risk.

Portable Planning Defaults

Include these implementation-phase defaults unless the user request, repository state, or issue risk calls for a narrower path: