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.