requirements-analysis

Expand sprint roadmaps into atomic requirements with acceptance criteria.

1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/mikall/FactoryX --skill requirements-analysis-mikall
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requirements-analysis
Source: https://github.com/mikall/FactoryX/tree/main/.claude/skills/requirements-analysis
Command: npx skills add https://github.com/mikall/FactoryX --skill requirements-analysis-mikall

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Expands sprint roadmaps into atomic, testable requirements, enabling clear handoffs to design, development, and QA, and ensuring alignment with master documents.

Core Features & Use Cases

  • Automates input scoping from the sprint roadmap into atomic requirements with explicit acceptance criteria
  • Ensures cross-artifact coherence by aligning functional and technical master documents
  • Supports PM and Architect reviews for early issue detection and decision traceability

Quick Start

Run the requirements-analysis workflow after sprint planning to convert the roadmap into actionable, atomic requirements.

Frequently Asked Questions about requirements-analysis

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

FAQPage Schema
How do I turn a sprint roadmap into atomic requirements with acceptance criteria?

You can expand sprint roadmaps into atomic, testable requirements by running an analysis workflow after sprint planning. This converts the roadmap into actionable functional requirements with explicit acceptance criteria and master document updates.

What is atomic requirements analysis in agile sprint planning?

Atomic requirements analysis is the process of expanding sprint roadmaps into granular, testable functional requirements during sprint planning. It ensures clear handoffs to development and QA by defining explicit acceptance criteria.

What prerequisites do I need to generate testable functional requirements?

Prerequisites for generating testable functional requirements include the sprint roadmap, a requirements-list, and existing analysis documents. These inputs allow the workflow to produce a draft requirements set and delta updates for master artifacts.

How does requirements traceability work with master documents during refinement?

Requirements traceability with master documents works by aligning functional and technical artifacts during refinement. This cross-artifact coherence ensures decision traceability and supports early issue detection during PM and Architect reviews.

When should I use automated requirements analysis for sprint planning?

Use automated requirements analysis during sprint planning and requirements refinement to convert roadmaps into actionable, atomic requirements. It ensures alignment with master documents and enables clear handoffs to design, development, and QA.