agentsclimarketplace
Sign in

043 planning github issues

Skill jabrena/plinth/skills/043-planning-github-issues

Use 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 ToolkitFrom its SKILL.md

Install
npx -y skills add jabrena/plinth --skill 043-planning-github-issues

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

4.0 KB, as published. Nobody here has run it

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 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-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 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 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

  1. Run interactive install gate

Check gh --version; if missing, stop and ask whether the user wants installation guidance before any issue operations.

  1. 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.

  1. 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.

  1. 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.

  1. 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.

What ships with it: 1 file

9.9 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most plan spec skills give

Counted across 1,360 of the 2,617 authors here whose files we hold, read 2026-09-06

  • Ask one question at a timein 73 of 1360
  • Write the spec using the templatein 22 of 1360
  • Ask clarifying questions if neededin 19 of 1360, across 18 files
  • Wait for user confirmation before proceedingin 19 of 1360
  • Save plans to the plans directoryin 17 of 1360, across 13 files
  • Check for product marketing context firstin 16 of 1360, across 5 files
  • Read the plan file completelyin 16 of 1360
  • Order tasks by dependencyin 16 of 1360
  • Gather context from the conversationin 15 of 1360, across 9 files
  • Explore the codebase instead of askingin 15 of 1360, across 13 files
  • Wait for explicit user approvalin 14 of 1360, across 13 files
  • Quiz the user on the breakdownin 13 of 1360, across 7 files

Said here and by no other author read

  • Run interactive install gate first
  • Verify gh availability for setup guidance
  • Keep issue inventory outside the agent context
  • Use GitHub issue numbers only for traceability
  • Request repository-owned planning artifact for analysis

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 626,045. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.