skills.rest
chaussky
chausskyCOMMUNITY
Explore all skills by this author →
GitHub

requirements_spec

Convert stakeholder insights into formal requirements using BABOK 7.1 templates.

40|15|Updated Apr 7, 2026
Search Tags:#requirements#bpmn#user-stories#business-analysis#use-cases#babok-7.1
One-click install
npx skills add https://github.com/chaussky/ainalyst --skill requirements-spec-chaussky
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements_spec
Source: https://github.com/chaussky/ainalyst/tree/main/skills/requirements_spec
Command: npx skills add https://github.com/chaussky/ainalyst --skill requirements-spec-chaussky

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Convert elicited stakeholder insights into formal, traceable requirements.

Core Features & Use Cases

  • Automatic generation of User Stories, Use Cases, and Functional/Non-Functional Requirements from elicitation artifacts
  • Templates aligned to BABOK 7.1 with traceability to 4.2/4.3 artifacts
  • Guidance for creating data dictionary and BPMN/process models

Quick Start

Supply the elicitation notes to begin generating formal, traceable requirements.

Frequently Asked Questions about requirements_spec

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

FAQPage Schema
How do I convert stakeholder elicitation notes into formal user stories and use cases?▼

To convert elicitation notes into formal user stories and use cases, supply the stakeholder insights to generate traceable requirements aligned with the BABOK 7.1 framework. The tool analyzes context and drafts artifacts using canonical templates.

What is the best way to structure business analysis requirements using BABOK 7.1?▼

The best way to structure business analysis requirements using BABOK 7.1 is to apply its canonical templates to produce functional requirements, business rules, and data definitions with built-in traceability to elicitation artifacts.

Can I generate BPMN process models and data dictionaries from stakeholder insights?▼

Yes, you can generate BPMN process models and data dictionaries from stakeholder insights. The tool provides step-by-step guidance to draft these process models and data definitions alongside standard user stories.

Do I need pre-structured notes to create traceable business requirements?▼

No, you do not need pre-structured notes to create traceable business requirements. You simply supply your raw elicitation notes, and the tool applies step-by-step analysis to draft formal artifacts and verify coverage.

How do I verify coverage for functional and non-functional requirements?▼

To verify coverage for functional and non-functional requirements, the tool applies the BABOK 7.1 framework to analyze context, draft artifacts, and ensure all generated requirements maintain traceability to source elicitation artifacts.

Related Skills

Explore More Data & Analytics Skills→
clovernguyen1010-ship-itclovernguyen1010-ship-it

ba-elicitation-review

Score elicitation outputs against an 8-criteria scorecard and list gaps.

Community
Advanced
Yukine5377Yukine5377

ba-usecase-list-gen

Group Use Cases into Epics from process inputs into Markdown.

Community
Advanced
Yukine5377Yukine5377

BA ERD Generation

Translate elicitation notes into Mermaid ER diagrams and a Data Dictionary.

Community
Advanced
chausskychaussky
40

requirements_verify

Automate BABOK 7.2 requirement quality checks and generate verification reports.

Community
Advanced