skills.rest
fx
fxCOMMUNITY
Explore all skills by this author →
GitHub

requirements-analyzer

Analyzes GitHub issues into structured requirements documents for implementation planning.

Updated Nov 2, 2025
Search Tags:#planning#clarification#acceptance criteria#github issues#requirements analysis#sdlc#scope brief
One-click install
npx skills add https://github.com/fx/skills --skill requirements-analyzer-fx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-analyzer
Source: https://github.com/fx/skills/tree/main/skills/requirements-analyzer
Command: npx skills add https://github.com/fx/skills --skill requirements-analyzer-fx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a raw GitHub issue into an actionable implementation plan requires gathering context, resolving ambiguities, and researching unfamiliar technologies. This Skill automates that analysis so downstream planning starts from complete, unambiguous requirements instead of guesswork. ## Core Features & Use Cases - Issue Analysis: Fetches GitHub issues via the gh CLI and extracts functional requirements, acceptance criteria, edge cases, and definition of done. - Clarification and Research: Uses AskUserQuestion to resolve ambiguities, plus WebSearch and WebFetch to research referenced technologies, APIs, and every URL in the issue. - Codebase Context: Reviews repo-scoped conventions (AGENTS.md, CONTRIBUTING, ADRs) and existing code patterns, then outputs a planner-ready requirements document with a verbatim Scope Brief. - Use Case: Point it at a vague feature request issue; it asks you targeted clarifying questions, researches the mentioned APIs, maps relevant files in your repo, and hands the planner a complete specification. ## Quick Start Analyze GitHub issue number 42 in this repository and produce a complete requirements document for the planner.

Frequently Asked Questions about requirements-analyzer

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

FAQPage Schema
How do I turn a GitHub issue into implementation requirements?▼

Fetch the issue with the gh CLI, extract functional and non-functional requirements, then clarify ambiguities with targeted questions. This Skill automates that flow and outputs a structured requirements document the planner skill consumes directly.

How to analyze vague feature requests before coding?▼

Use AskUserQuestion to resolve unclear scope, acceptance criteria, and technical approach before finalizing requirements. Combine this with WebSearch and WebFetch to research referenced technologies and every URL in the issue.

Does requirements analysis include codebase context?▼

Yes. The Skill reviews repo-scoped files like AGENTS.md, CONTRIBUTING, and ADRs, finds similar existing implementations with file paths, and documents conventions the implementation must follow. It never reads home-level config files.

What happens when no issue URL is provided?▼

The Skill checks GitHub project boards for Todo items first, then reviews recently merged PRs to select the next logical issue based on priority labels, dependencies, and absence of blockers.

When should I not use automated requirements analysis?▼

Skip it for trivial changes where the request is already unambiguous, or when requirements come from sources other than GitHub issues. The Skill is optimized for issue-driven planning handoff, not general documentation.

Related Skills

Explore More Software Engineering Skills→
declanshanaghydeclanshanaghy

file-issue

Generate labeled GitHub issues with structured bodies and project-board placement.

Community
Advanced
peteromalletpeteromallet
97

writing-plans

Create implementation plans with tasks, file paths, tests, and verification steps.

Community
Advanced
daddiadaddia
1

review-code

Review branch or PR diffs for quality, correctness, security, and standards.

Community
Advanced
evanklemevanklem
417

evanflow-prd

Synthesize a comprehensive PRD from project context and ADRs into docs/specs.

Community
Advanced