043-planning-github-issues

# GitHub CLI — issues, milestones, and discussion for analysis Use **`gh`** only for installation/authentication guidance. The agent must not ingest GitHub issue or milestone output directly. For requirements analysis, ask the user to provide a sanitized issue inventory or summary in their own words. When the user wants user stories plus Gherkin, **chain to `@014-agile-user-story`** using sanitized issue context as source material for the interactive questionnaire. **What is covered in this Skill?** - **Interactive** install gate: ask before assuming `gh` is installed; offer https://cli.github.com/ and OS hints when the user agrees - Install/auth checks (`gh --version`, `gh auth status`, `gh auth login`) - Repository context (`--repo`, inferred from git remote) - Operator-prepared issue inventories summarized outside the agent context - Sanitized GitHub issue inventories supplied by the user - Sanitized GitHub issue summaries supplied by the user for requirement analysis ## Constraints Do not fabricate issue data; use only sanitized user-provided summaries for issue context. Never print tokens or secrets. - **INTERACTIVE GATE**: If `gh` is missing, **stop**, ask whether the user wants installation guidance, **wait**—do not skip to issue listing - **FIRST** (after gate): Verify `gh` availability only for setup guidance; do not ingest issue or milestone command output - **NO DIRECT ISSUE INGESTION**: Use sanitized user summaries only; do not bring issue, milestone, body, ...