aet-req-analysis

Transforms raw requirements into structured specifications through Socratic dialogue and staged workflows.

7.1k|1.1k|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/openJiuwen-ai/jiuwenswarm --skill aet-req-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aet-req-analysis
Source: https://github.com/openJiuwen-ai/jiuwenswarm/tree/main/jiuwenswarm/agents/harness/code/rails/sdd/design_rail/skills/aet-req-analysis
Command: npx skills add https://github.com/openJiuwen-ai/jiuwenswarm --skill aet-req-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Raw requirements from users, tickets, or meeting notes are often ambiguous, incomplete, and unstructured, making downstream design and development error-prone. This Skill converts raw requirements (RR) into a rigorous, structured requirements analysis specification (IR) with functional/non-functional requirements, acceptance criteria, and test cases.

Core Features & Use Cases

  • Socratic Requirements Elicitation: Clarifies ambiguities through iterative dialogue, behavior path analysis (happy path, alternatives, exceptions), and blind-spot discovery before any document is written.
  • Template-Driven Document Generation: Assembles requirement specification templates dynamically via Node.js scripts, applying EARS syntax and placeholder conventions for unsourced quantitative values.
  • Checklist-Based Review Pipeline: Generates a dynamic review checklist and supports a staged review workflow with severity-graded scoring (Pass / Conditional Pass / Fail).
  • Use Case: A product manager pastes a vague feature request from a GitHub issue; the Skill interviews them to resolve ambiguities, then produces a complete requirements analysis specification with prioritized FR/NFR lists, acceptance criteria, and test cases.

Quick Start

Ask the agent to analyze your raw requirement description and generate a structured requirements analysis specification document.

Frequently Asked Questions about aet-req-analysis

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

FAQPage Schema
How do I turn a vague feature request into a structured requirements specification?

Provide the raw requirement text (issue, ticket, or meeting note) as input. The skill runs a Socratic elicitation stage to resolve ambiguities, then generates a specification with functional requirements, non-functional requirements, acceptance criteria, and test cases.

What is the EARS approach to writing requirements?

EARS (Easy Approach to Requirements Syntax) constrains requirement statements to deterministic templates like "When [trigger] occurs, the [system] shall [action]". This skill applies EARS to make specifications normative rather than merely descriptive.

Does this requirements skill make design or architecture decisions?

No. It explicitly prohibits design decisions, technology selection, and module partitioning. It only describes what the system should do, never how to implement it, keeping requirements independent of the technology stack.

What runtime is needed to use the template assembly scripts?

The scripts require Node.js version 18 or higher. Run assemble-template.mjs with the argument req-analysis to produce the document template, and assemble-checklist.mjs to produce the review checklist.

How are unverified quantitative values handled in generated specifications?

Any quantitative value without a source must be written as a placeholder token in the form [[PH:id | rec:value | why:reason]] instead of a bare number. Downstream review can scan these tokens to enumerate unfilled placeholders.