topic-to-issue

Investigate a topic. If — and only if — it leaves a concrete action that can't be resolved on the spot, capture it as an actionable GitHub issue. Otherwise just answer; do not file noise.

Steps

1. Investigate the topic.

   • Search the current repo first (Grep/Glob/Read) and any docs it ships.
   • Reach for the web (WebSearch/WebFetch) only when the topic isn't codebase-internal.
   • Goal: establish the facts so the ticket reflects a finished investigation, not a guess.

2. Decide: file or not. Open an issue ONLY when the investigation leaves a concrete action that can't be done right now — needs another person, another repo, or is deferred work. If you can just answer or fix it now, do that and stop. State the verdict either way.

3. Draft using the template below. Keep the What to do line imperative and scoped. Add the Open question line only when something genuinely needs deciding first. Drop Pointers if there's nothing to link. Fill Done when with checkable outcomes.

4. Confirm before creating. Show the full drafted issue (title + body) and the target repo. Wait for the user's go-ahead. Creating an issue is outward-facing — never gh issue create without confirmation.

5. Create it. Write the body to a temp file (preserves markdown/backticks/checkboxes), then create against the current repo. Report back the issue URL.