To Issues

Break a plan into independently-grabbable issues using vertical slices (tracer bullets).

Process

1. Choose where to publish

The default is Local markdown — files under .scratch/ in this repo, no remote needed. Don't probe git remote; only publish to GitHub or GitLab if the user explicitly asks.

• Ask the user where to publish, with Local markdown pre-selected:
  • Local markdown (default) — files under .scratch/<feature-slug>/issues/ in this repo
  • GitHub — GitHub issues (gh CLI), only if requested
  • GitLab — GitLab issues (glab CLI), only if requested
• Carry the choice into step 6. For GitHub or GitLab, follow the exact conventions and triage-label mappings in docs/agents/issue-tracker.md if it covers that backend; otherwise use the conventions in <destination-conventions> below. Run /setup-matt-pocock-skills to configure those conventions and a triage-label vocabulary.

2. Gather context

Work from whatever is already in the conversation context. If the user passes an issue reference (issue number, URL, or path) as an argument, fetch it from the issue tracker and read its full body and comments.