requirements-analyst

Analyze requirements from Confluence pages and decompose them into actionable development tasks.

Updated Oct 2, 2025
One-click install
npx skills add https://github.com/YuriiYInno/Innogram --skill requirements-analyst-yuriiyinno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-analyst
Source: https://github.com/YuriiYInno/Innogram/tree/main/.codex/skills/requirements-analyst
Command: npx skills add https://github.com/YuriiYInno/Innogram --skill requirements-analyst-yuriiyinno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning raw requirements from Confluence pages, specs, or user requests into a structured, validated task breakdown is time-consuming and error-prone, often leaving gaps discovered only during implementation. ## Core Features & Use Cases - Requirements Extraction: Gathers functional, non-functional, business rule, integration, and security requirements from Confluence documents or direct user input with clarifying questions. - Task Decomposition: Breaks each requirement into backend tasks (entities, repositories, services, controllers, DTOs), frontend tasks (components, state, API integration), and testing tasks. - Completeness Validation: Runs a checklist covering happy paths, error cases, edge cases, security, and performance, then produces a gap analysis. - Use Case: Paste a Confluence feature spec for user authentication and receive a numbered requirements document saved to tasks/TASK-001/ with a full task breakdown and identified gaps, ready to hand off to design or planning. ## Quick Start Ask the assistant to analyze the requirements from your Confluence page and break the feature down into actionable tasks.

Frequently Asked Questions about requirements-analyst

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

FAQPage Schema
How do I break down a feature spec into development tasks?▼

Provide the spec or Confluence content and the skill categorizes each requirement, then decomposes it into backend tasks (entities, services, controllers, DTOs), frontend tasks (components, state, API calls), and testing tasks. The result is saved as a structured requirements document.

How to analyze requirements from a Confluence page?▼

Share the Confluence page content or link and the skill extracts functional and non-functional requirements along with acceptance criteria. It asks clarifying questions one at a time when information is missing or ambiguous.

What output does the requirements analysis produce?▼

It writes a markdown requirements document to tasks/TASK-{N}/requirements-analyst-requirements.md containing categorized requirements, a task breakdown table, gap analysis, and suggested next steps. A counter file tracks task numbering across runs.

Does it validate that requirements are complete?▼

Yes, it runs a validation checklist covering happy paths, error cases, edge cases, security, performance, and testing strategy. Any unclear or missing information is recorded in a gap analysis section of the output document.

When should I use brainstorming or architecture instead of requirements analysis?▼

Use requirements analysis first when the feature scope is unclear or undocumented. If requirements are already well-defined, skip directly to architecture decisions or implementation planning, which the skill suggests as alternative next steps.