Enters a structured planning mode that considers the project's architecture pattern before producing an implementation plan. Instead of jumping straight to code, this command forces a deliberate pause to:

Plans are living documents -- if something goes sideways during implementation, stop and re-plan rather than pushing through a broken approach.

Skip planning for: Single-file changes, simple bug fixes, typo corrections, config tweaks.

Check for an approved spec covering this task — if one exists, it is the source of truth: map its acceptance criteria to plan steps and skip ahead to Step 2. If the feature is spec-worthy (too big to describe in one sentence) and no spec exists, recommend first instead of planning on assumptions. Otherwise, clarify what the user wants to build with focused questions. Do not assume requirements that were not stated.

Use the skill to determine the project's architecture:

Identify every layer, module, and boundary the task touches:

Output a numbered plan with this structure:

undefined

Architecture: [Detected architecture] Affected layers: [List] Estimated steps: [Count]

Present the plan and ask: "Does this plan look right, or should I adjust anything?" Revise until the user confirms. Only then proceed to implementation.

Architecture: Vertical Slice Architecture Affected layers: Features/, Infrastructure/Persistence/, Tests/ Estimated steps: 6

Does this plan look right, or should I adjust anything?

undefined