requirements-analysis

Name: requirements-analysis
Availability: InStock
Author: magicpro97

Transform raw business needs into a structured, traceable requirements specification.

8|3|Updated Jun 7, 2026

Search Tags:#traceability #requirements engineering #business analysis #requirements management #structured specification

Ready to run

npx skills add https://github.com/magicpro97/vibeflow --skill requirements-analysis-magicpro97

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirements-analysis
Source: https://github.com/magicpro97/vibeflow/tree/main/templates/skills/requirements-analysis
Command: npx skills add https://github.com/magicpro97/vibeflow --skill requirements-analysis-magicpro97

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Transforms ambiguous, raw business inputs into structured requirements, eliminating the need for repeated interpretation and ensuring a unified understanding of the project's objectives.

Core Features & Use Cases

Ambiguity Resolution: Clears ambiguity and gaps in raw input files to produce a clear, structured requirements specification.
Traceability: Ensures each requirement can be traced back to its source, promoting accountability and maintainability.
Automated Input Inventory: Reads and tags files for source and date, streamlining the input processing phase.
Output Structure: Outputs requirements structured by feature area or user role, including a traceability table.
Self-Review and Validation: Performs self-review and verification against defined success criteria before finalizing outputs.

Quick Start

Execute the vf run requirements-analysis command and provide the necessary input path(s) to begin processing.

Frequently Asked Questions about requirements-analysis

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

FAQPage Schema

How do I structure raw business needs into traceable requirements specifications?▼

To structure raw business needs into traceable requirements specifications, the skill reads input files, classifies them by feature area or user role, and generates a traceability table linking each item to its source.

How does requirements traceability work for business analysis inputs?▼

Requirements traceability for business analysis inputs works by tagging source files and mapping deduplicated items back to their origins. This promotes accountability and maintainability throughout the engineering lifecycle.

What is the best way to resolve ambiguity and gaps in raw requirements engineering inputs?▼

The best way to resolve ambiguity and gaps in raw requirements engineering inputs is through automated self-review and validation. This clears ambiguity and fills gaps explicitly before finalizing structured outputs.

Do I need a specific project context file to perform structured specification for business analysis?▼

Yes, you need a project-specific file named .vibeflow/PROJECT_CONTEXT.md to perform structured specification. This file provides the necessary project information to accurately classify and process requirements.

What are the limitations when trying to deduplicate and classify structured requirements?▼

A limitation when trying to deduplicate and classify structured requirements is the dependency on a properly configured .vibeflow/PROJECT_CONTEXT.md file. Without this context, the skill cannot ensure accurate traceability or gap filling.