Skill: To Issues

Use this skill to convert plans into small execution units.

Issue Rules

• Each issue must deliver one user-visible or verifiable slice.
• Avoid issues named by layers only, such as "create database" or "build UI".
• Include acceptance criteria and verification command when known.
• Keep dependencies explicit.
• Prefer 3-7 issues for medium work.

Issue Template

• Title: action + outcome.
• Context: why this matters.
• Scope: included work.
• Out of scope: excluded work.
• Acceptance criteria: testable bullets.
• Verification: commands or manual checks.
• Dependencies: prior issues if any.