skills.rest
aizhimou
aizhimouCOMMUNITY
Explore all skills by this author →
Website𝕏@aizhimougGitHub

requirements-analysis

Analyze product and technical requirements for PigeonPod with phased delivery.

1.2k|95|Updated Aug 23, 2025
Search Tags:#planning#architecture#requirements#analysis#feasibility#risk#mcp-context7
One-click install
npx skills add https://github.com/aizhimou/pigeon-pod --skill requirements-analysis-aizhimou
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-analysis
Source: https://github.com/aizhimou/pigeon-pod/tree/main/.agent/skills/requirements-analysis
Command: npx skills add https://github.com/aizhimou/pigeon-pod --skill requirements-analysis-aizhimou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PigeonPod teams need a disciplined way to analyze and validate product and technical requirements, ensuring alignment with architecture, feasibility, scope, and delivery impact before committing resources.

Core Features & Use Cases

  • Restate and clarify a given requirement to establish a precise problem statement.
  • Classify the requirement into feature, enhancement, non-functional, integration, or migration, and evaluate user value and business impact.
  • Propose phased delivery with an MVP, next steps, and later work, including dependency and risk considerations.

Quick Start

Restate the given requirement, assess feasibility and architecture fit, and outline a phased MVP/Next/Later delivery plan.

Frequently Asked Questions about requirements-analysis

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

FAQPage Schema
How do I analyze product requirements for architecture fit and feasibility?▼

To analyze product requirements, you restate the problem, classify the requirement type, and evaluate user value against architecture constraints. This validates feasibility and data impact before proposing a phased MVP delivery plan.

What is the best way to structure phased delivery for technical requirements?▼

Structuring phased delivery involves dividing validated requirements into MVP, next steps, and later work. This approach incorporates dependency checks and risk considerations to ensure aligned, incremental technical delivery.

How do I classify requirements into features, integrations, or migrations?▼

Classifying requirements involves evaluating the core problem statement to categorize work as a feature, enhancement, non-functional need, integration, or migration, assessing both user value and business impact.

Can I validate technical dependencies and risks using Context7 and MCP constraints?▼

Yes, you validate technical dependencies and risks by leveraging Context7 and MCP constraints. This ensures local docs and architectural limitations are checked before committing resources to delivery.

How do I assess data impact when planning a new product requirement?▼

Assessing data impact requires applying a structured framework to the clarified requirement. This validates how the proposed feature or enhancement affects existing data structures before outlining the MVP.

Related Skills

Explore More Software Engineering Skills→
arittrarittr
19

writing-specs

Generate lean feature specifications defining WHAT and WHY with linked external docs.

Community
Intermediate
alirezarezvanialirezarezvani
110

roadmap-generator

Convert architecture designs into phased roadmaps with Epics, Stories, and Tasks.

Community
Advanced
rjroyrjroy
6

ddp

Generate Mermaid diagrams for data flows, class relationships, and architectures.

Community
Basic
tikazyqtikazyq
5

implementation-sequencer

Generates code build sequences and sprint divisions from project dependencies and goals.

Community
Intermediate