analyze-requirements

Name: analyze-requirements
Availability: InStock
Author: NESNILNEHC

Convert vague ideas into validated requirements with acceptance criteria.

7|3|Updated Jan 23, 2026

Search Tags:#documentation #requirements #validation #discovery #handoff #analyze

Ready to run

npx skills add https://github.com/nesnilnehc/ai-cortex --skill analyze-requirements-nesnilnehc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analyze-requirements
Source: https://github.com/nesnilnehc/ai-cortex/tree/main/skills/analyze-requirements
Command: npx skills add https://github.com/nesnilnehc/ai-cortex --skill analyze-requirements-nesnilnehc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams translate vague ideas or incomplete requirements into a validated, testable requirements document by guiding a structured diagnostic progression through RA0–RA5, ensuring no design or implementation decisions are made before validation.

Core Features & Use Cases

Structured diagnostic progression through RA0 to RA5 to surface the true problem and gather requirements.
Output of a validated requirements document at docs/requirements-planning/<topic>.md with a clear constraint inventory and acceptance criteria.
Handoff readiness for design-solution once requirements are validated, with traces to upstream/downstream skills.

Quick Start

Provide your vague idea or requirement, and I will begin the RA0 diagnostic to validate it before design.

Frequently Asked Questions about analyze-requirements

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

FAQPage Schema

How do I turn a vague product idea into a validated requirements document?▼

To turn a vague idea into a validated requirements document, apply a structured RA0–RA5 diagnostic dialogue to surface the true problem, define acceptance criteria, and document constraints before any design begins.

What is the best way to write testable requirements for a new feature request?▼

The best way to write testable requirements is to guide the feature request through a structured diagnostic progression, ensuring validation and outputting a scoped V1 boundary with a clear constraint inventory.

How do I generate acceptance criteria and a risk inventory for project planning?▼

You generate acceptance criteria and a risk inventory by validating the project scope through a structured diagnostic, outputting the results to a docs/requirements-planning/<topic>.md artifact.

Can I use a structured dialogue to prevent premature design decisions during discovery?▼

Yes, you can use an RA0–RA5 structured dialogue to prevent premature design decisions, ensuring no implementation choices are made until the requirements are fully validated and scoped.

When do I need a requirements validation process instead of jumping straight into design?▼

You need a requirements validation process when handling new projects or incomplete requirements that lack clarity, ensuring you establish a scoped V1 boundary and handoff readiness before design begins.

Does this requirements discovery method output a standard file format for handoff?▼

Yes, this requirements discovery method outputs a docs/requirements-planning/<topic>.md artifact containing the validated requirements, ensuring handoff readiness for design-solution with clear upstream and downstream traces.