To Issues

Turn a roadmap or plan into implementation-ready issues. Prefer thin vertical slices that deliver a complete, verifiable path through the product rather than horizontal layer work.

Workflow

1. Resolve the target issue tracker.

   • Use repository context, the current git remote, GH_REPO, or the user's explicit repository.
   • If the target tracker is ambiguous, ask one concise question before publishing issues.
   • Discover supported metadata before applying labels, issue types, sub-issues, dependencies, milestones, or project fields.

2. Gather source context.

   • Work from the roadmap, plan, spec, PRD, or parent issue already in context.
   • If the user provides an issue number, URL, or path, read the full body and relevant comments before drafting.
   • If the codebase has domain docs, glossary, ADRs, or existing related issues, use their vocabulary and constraints.