to-issues

Slice the plan vertically so each issue is a tracer bullet touching all layers from domain to entry point. Order issues by dependency, format them with acceptance criteria and test commands, then create them with gh issue create after user approval.

A vertical slice is a thin end-to-end piece of work that touches all necessary layers and delivers observable value on its own. It contrasts with horizontal slices like adding all domain entities at once, which delay feedback and integration.

A plan should produce at most 8 issues, each representing no more than one day of work. If more are needed, split the work into phases; if an issue is too large, slice it thinner.

Yes, the GitHub CLI supports issue creation via gh issue create. This workflow presents the full issue list as a numbered table for approval first, then creates the confirmed issues with the needs-triage label by default.

Vertical slicing is less suitable when the plan is still vague or scope boundaries are unclear. In that case, clarify scope first with a few targeted questions and check the roadmap and existing issues for overlap before slicing.