name	decompose-to-issues
description	Break high-level work into independently executable GitHub issues using vertical slices. Use when a plan, PRD, roadmap item, or vague feature needs issue-sized execution units.

Decompose To Issues

Use decomposition as context control, not project-management ceremony.

Identify the user-visible or operational outcome.
Split by vertical slices that can be implemented, reviewed, and verified independently.
Put shared setup before dependent slices only when it unlocks multiple issues.
Mark dependencies explicitly.
Keep each issue small enough for a fresh agent to complete in one focused pass when possible.

Each issue should include:

Avoid horizontal slices like "build backend" and "build frontend" unless the architecture truly requires it.
Do not create issues that require inherited conversation context to understand.
Create follow-up issues for scope discovered during implementation.

name	decompose-to-issues
description	Break high-level work into independently executable GitHub issues using vertical slices. Use when a plan, PRD, roadmap item, or vague feature needs issue-sized execution units.

Use decomposition as context control, not project-management ceremony.

Identify the user-visible or operational outcome.
Split by vertical slices that can be implemented, reviewed, and verified independently.
Put shared setup before dependent slices only when it unlocks multiple issues.
Mark dependencies explicitly.
Keep each issue small enough for a fresh agent to complete in one focused pass when possible.

Each issue should include:

Avoid horizontal slices like "build backend" and "build frontend" unless the architecture truly requires it.
Do not create issues that require inherited conversation context to understand.
Create follow-up issues for scope discovered during implementation.

decompose-to-issues