What problem does it solve? Writing GitHub issues that clearly state the current situation and direction—without leaking implementation details that belong in pull requests—is hard to do consistently. This Skill enforces a structured issue format (As-is, To-be, Note, Checklist, Sub-issues), typed titles with emoji, and safe filing through the gh CLI only after explicit approval. ## Core Features & Use Cases - Structured issue bodies: Generates the five H1 sections in order, writing only sections that carry content, with rules for when H2 subsections, tables, and one-target-per-line checkboxes apply. - Hub and sub-issue support: Writes hub issues that gather children with no checklist of their own, files sub-issues via gh issue create --parent, and fills in bodies of sub-issues GitHub created empty. - Approval-gated filing: Shows title and body in fenced blocks first, files with gh issue create --body-file only after you say yes, and hands over the command when gh is unavailable. - Use Case: Ask for an issue to track raising a dependency across several packages, and receive a typed title, an observed As-is section, a per-package checklist, and a ready-to-run gh command. ## Quick Start Write a GitHub issue for adding a quick start guide to the docs directory and file it once I approve the text.