requirements-analysis

Convert vague ideas into structured requirements and testable user stories.

8|2|Updated Feb 9, 2026

Search Tags:#templates #requirements #traceability #user-stories #acceptance-criteria #stakeholders

Ready to run

npx skills add https://github.com/mikeparcewski/wicked-garden --skill requirements-analysis-mikeparcewski

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirements-analysis
Source: https://github.com/mikeparcewski/wicked-garden/tree/main/skills/product/requirements-analysis
Command: npx skills add https://github.com/mikeparcewski/wicked-garden --skill requirements-analysis-mikeparcewski

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured requirements elicitation from discovery through documentation, enabling teams to turn vague ideas into actionable deliverables.

Core Features & Use Cases

Graph-mode requirements by default for complexity >= 3 or compliance projects, with --monolith to force a single-file format
As a product manager, I want to define stakeholder needs and convert them into precise user stories with acceptance criteria
Supports traceability across outcomes, design, QA/test phases, and references to source documents
Reuses templates and example references from the refs directory to accelerate documentation

Quick Start

Copy the requirements templates and begin documenting your feature with user stories and acceptance criteria.

Frequently Asked Questions about requirements-analysis

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

FAQPage Schema

How do I turn vague ideas into structured user stories with acceptance criteria?▼

To turn vague ideas into structured user stories, you elicit stakeholder needs and convert them into precise user stories with testable acceptance criteria. This approach produces a graph-based requirements model by default for complex projects.

What is requirements traceability and when do I need it for compliance projects?▼

Requirements traceability links outcomes, design, and QA test phases back to source documents. You need traceability for compliance initiatives or complex projects where validation checks must verify that every requirement is covered and tested.

How do I structure requirements for complex projects using a graph-based model?▼

Structuring requirements for complex projects uses a default graph-based requirements model to map interconnected outcomes and validation checks. You can force a single monolithic document format by requesting a monolith output instead.

Can I use templates to accelerate user story and acceptance criteria documentation?▼

You can reuse provided templates and example references to accelerate documenting your feature with user stories and acceptance criteria. Copying these templates allows you to quickly structure stakeholder needs into testable deliverables.

Does this requirements analysis approach support stakeholder elicitation from discovery through documentation?▼

Requirements analysis supports stakeholder elicitation from discovery through documentation, enabling teams to define needs and convert them into actionable deliverables. It produces structured requirements and testable user stories suitable for complex projects.

What is the best way to document compliance initiatives with testable user stories?▼

The best way to document compliance initiatives is to generate a graph-based requirements model that supports validation checks and traceability references. This method ensures stakeholder needs convert into precise user stories with acceptance criteria schemas.