How are success criteria defined?

Each requirement document includes a Success Criteria section that maps specific outcomes to measurable targets and measurement methods.

How does the ID convention work?

It uses feature-scoped, gap-friendly IDs (e.g., FR-010, FR-020) which allow for new requirements to be inserted later without renumbering the entire document.

Does it handle non-functional requirements?

Yes, it specifically categorizes and documents Security (SEC), Performance (PERF), and Accessibility (ACC) requirements with specific targets and metrics.

What inputs does the Requirements Analyst skill need?

It is designed to process Discovery Briefs and Intake documents to extract stakeholder goals, technical needs, and project constraints.

Can this skill help with project scope creep?

Absolutely. It requires the explicit listing of 'Out of Scope' items and identifies 'P0' launch blockers to keep the team focused on core objectives.

Requirements Analyst

Name: Requirements Analyst
Author: violetio

byvioletio

Collaboration Tools

Transforms discovery findings into structured, actionable requirements documents with measurable success criteria.

About

The Requirements Analyst skill bridges the gap between initial project discovery and technical execution by formalizing stakeholder needs into a comprehensive source of truth. It automatically identifies functional and non-functional requirements—including security, performance, and accessibility—while establishing stable, gap-friendly ID conventions and testable acceptance criteria. This skill is essential for technical product managers and lead developers who need to maintain strict scope control, surface potential architectural conflicts early, and ensure that every feature has a clear definition of done.

Key Features

Automated generation of structured functional and non-functional requirement tables.
Definition of measurable success metrics and testable acceptance criteria for QA.
Comprehensive scope management including constraints, dependencies, and out-of-scope lists.
0 GitHub stars
Integrated P0/P1/P2 prioritization framework to identify launch-critical features.
Standardized gap-friendly ID convention for stable requirement tracking across versions.

Use Cases

Identifying and documenting technical dependencies and potential requirement conflicts for cross-functional teams.
Converting messy discovery notes or stakeholder intake forms into a formal technical specification.
Establishing security and accessibility benchmarks for a new feature before development begins.

About

Key Features

Automated generation of structured functional and non-functional requirement tables.
Definition of measurable success metrics and testable acceptance criteria for QA.
Comprehensive scope management including constraints, dependencies, and out-of-scope lists.
0 GitHub stars
Integrated P0/P1/P2 prioritization framework to identify launch-critical features.
Standardized gap-friendly ID convention for stable requirement tracking across versions.

Use Cases

Identifying and documenting technical dependencies and potential requirement conflicts for cross-functional teams.
Converting messy discovery notes or stakeholder intake forms into a formal technical specification.
Establishing security and accessibility benchmarks for a new feature before development begins.