jabrena/plinth / skills/043-planning-github-issues
043-planning-github-issues
UnverifiedUse when you need GitHub CLI (`gh`) installation/authentication guidance and an operator-only GitHub issue inventory workflow. The agent does not ingest GitHub issue, milestone, body, comment, title, label, or summary text; requirements analysis must use repository-owned planning artifacts, with issue numbers only for traceability. This should trigger for requests such as GitHub issue inventory workflow; GitHub CLI setup for issues; Prepare issue traceability lists; Analyze repository planning artifacts linked to GitHub issues. Part of Plinth Toolkit
GitHub CLI — issues, milestones, and discussion for analysis
Use gh only for installation/authentication guidance and operator-side workflow instructions. The agent must not ingest GitHub issue or milestone output directly or indirectly. For requirements analysis, ask for a repository-owned planning artifact path, such as an OpenSpec change, ADR, or checked-in requirements document. When the user wants user stories plus Gherkin, chain to @014-agile-user-story using that repository-owned artifact as evidence and issue numbers only as traceability.
What is covered in this Skill?
- Interactive install gate: ask before assuming
ghis 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-side issue inventory preparation kept outside the agent context
- Issue-number traceability lists without issue prose
- Repository-owned planning artifact handoff for requirement analysis
Constraints
Do not fabricate issue data and do not ingest issue prose. Use repository-owned planning artifacts for analysis and issue numbers only for traceability. Never print tokens or secrets.
- INTERACTIVE GATE: If
ghis missing, stop, ask whether the user wants installation guidance, wait—do not skip to issue listing - FIRST (after gate): Verify
ghavailability only for setup guidance; do not ingest issue or milestone command output - NO ISSUE TEXT INGESTION: Do not bring issue, milestone, body, comment, title, label, or summary text into the agent context
- TRACEABILITY ONLY: Use GitHub issue numbers only as traceability identifiers; analyze repository-owned planning artifacts instead of issue content
When to use this skill
- GitHub issue inventory workflow
- GitHub CLI setup for issues
- Prepare GitHub issue traceability list
- Analyze repository planning artifacts linked to GitHub issues
- Keep GitHub issue text outside agent context
Workflow
- Run interactive install gate
Check gh --version; if missing, stop and ask whether the user wants installation guidance before any issue operations.
- Explain authentication and repository context
Explain how the user can verify gh auth status and repository context locally. Keep issue and milestone exports outside the agent context.
- Keep issue inventory outside the agent context
Ask the repository maintainer to prepare any issue inventory outside the agent context. They must not provide issue prose to the agent. If traceability is needed, accept only issue numbers.
- Request repository-owned planning artifact for analysis
Do not retrieve or accept GitHub issue, milestone, body, comment, title, label, or summary text. Ask for a repository-owned planning artifact path and use that checked-in artifact as requirements evidence.
- Chain to user story workflow when requested
When user asks for user stories and Gherkin from issues, hand off to @014-agile-user-story using a repository-owned planning artifact as evidence and issue numbers only for traceability.
Reference
For detailed guidance, examples, and constraints, see references/043-planning-github-issues.md.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 463k | Updated | Claude CodeCodex | Verified | Install |
| discernment-nudgeanthropics/skillsAfter you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format. | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |
| internal-commsanthropics/skillsA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.). | Stars: 195k | Updated | Claude CodeCodex | Verified | Install |