agile-requirement-analyzer

Transform customer requirements into structured Epics, Features, and Stories.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/Gct-Zxli/GCTReporter --skill agile-requirement-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agile-requirement-analyzer
Source: https://github.com/Gct-Zxli/GCTReporter/tree/main/.claude/skills/agile-requirement-analyzer
Command: npx skills add https://github.com/Gct-Zxli/GCTReporter --skill agile-requirement-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translates vague customer requirements into structured Agile artifacts (Epics, Features, Stories) with a repeatable workflow, ensuring traceability and high-quality backlog items.

Core Features & Use Cases

  • 6-step RTGO workflow: requirement clarification, level determination, Epic analysis, user story generation, INVEST evaluation, and acceptance criteria generation.
  • Built-in INVEST quality checks and MoSCoW prioritization to guide backlog refinement and sprint planning.
  • Learning memory and breakpoint resume to adapt to preferences and continue where you left off.

Quick Start

Provide the customer’s raw requirements to start the full agile requirement analysis flow.

Frequently Asked Questions about agile-requirement-analyzer

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

FAQPage Schema
How do I turn vague customer requirements into structured agile Epics and user stories?

To turn vague customer requirements into structured agile Epics, this Skill applies a 6-step RTGO workflow that clarifies needs, determines levels, and generates ready-to-use user stories with validated acceptance criteria.

What is the INVEST criteria check for agile backlog grooming?

The INVEST criteria check for agile backlog grooming is a built-in quality gate that evaluates generated user stories to ensure they are Independent, Negotiable, Valuable, Estimable, Small, and Testable before sprint planning.

How to generate acceptance criteria for user stories from raw requirements?

To generate acceptance criteria for user stories, input raw customer requirements to trigger the automated workflow, which validates and outputs structured criteria compliant with organizational standards.

Does this agile requirement analysis support MoSCoW prioritization for sprint planning?

Yes, agile requirement analysis supports MoSCoW prioritization to guide backlog refinement and sprint planning, categorizing generated Epics and Features by Must-have, Should-have, Could-have, and Won't-have.

Can I resume agile requirement analysis if I stop halfway through the workflow?

You can resume agile requirement analysis using the built-in breakpoint resume feature, allowing you to continue Epic generation and INVEST evaluation exactly where you left off without losing context.

What is the best way to ensure traceability across Epics, Features, and Stories?

The best way to ensure traceability across Epics, Features, and Stories is to use a repeatable workflow that applies automated quality gates and hierarchical level determination to maintain structural dependency links.