issue-requirements

Extract requirements and acceptance criteria from GitHub issues and linked references.

8.0k|560|Updated Mar 3, 2022
One-click install
npx skills add https://github.com/podman-desktop/podman-desktop --skill issue-requirements
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-requirements
Source: https://github.com/podman-desktop/podman-desktop/tree/main/.agents/skills/issue-requirements
Command: npx skills add https://github.com/podman-desktop/podman-desktop --skill issue-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Understanding what a GitHub issue actually asks for requires reading the issue body, every comment, and all linked issues and PRs — a slow, error-prone manual process. This Skill automates that collection and produces a structured requirements document that a downstream agent or developer can act on directly.

Core Features & Use Cases

  • Recursive issue traversal: Fetches the root issue, discovers linked issues and PRs from bodies, comments, and timeline cross-references, then recurses one level deeper.
  • Structured requirements output: Produces a consistent Markdown report with feature summary, acceptance criteria, scenarios, dependencies, open questions, and cited references.
  • Strict no-invention rule: Every criterion and scenario is traceable to an explicit statement in the issue, a comment, or a linked PR — nothing is assumed or fabricated.
  • Use Case: Before implementing a feature requested in podman-desktop issue #1234, run this Skill to gather all acceptance criteria and design decisions scattered across comments and linked PRs into one actionable document.

Quick Start

Extract the requirements from GitHub issue #1234 in this repository, including all linked issues and PRs.

Frequently Asked Questions about issue-requirements

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract acceptance criteria from a GitHub issue?

Fetch the issue with gh issue view including comments, then scan the body and comments for explicit statements using words like should, must, and expected. This Skill automates that process and outputs numbered, verifiable acceptance criteria with source citations.

How to find all issues and PRs linked to a GitHub issue?

Scan the issue body and comments for #number references, owner/repo#number references, and URLs, then query the timeline API for cross-referenced events. The Skill follows only these explicit links and recurses one level deeper.

What input formats does this Skill accept for GitHub issues?

It accepts a full GitHub issue URL, a short owner/repo#123 reference, or a bare #123 issue number when working inside a cloned repository. The gh CLI must be installed and authenticated.

Does this Skill write code or run tests based on the issue?

No. It only collects and organizes requirements explicitly stated in the issue and its linked references. Writing code, running tests, and debugging are explicitly out of scope and left to downstream agents.

What happens if a GitHub issue has very little detail?

The output will be sparse by design. The Skill never invents scenarios or criteria; missing information is flagged in the Open Questions section so a downstream agent can investigate further.