requirements-analysis

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.

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.

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.

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.

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.