analyze-requirements

To generate a functional requirements document, input your project description and the skill parses actors, functionalities, and non-functional needs to produce structured markdown files for development teams.

Automated requirements analysis extracts project overview, actors, and constraints from user descriptions, asking clarifying questions to resolve scope ambiguities before creating comprehensive markdown documentation.

Yes, you can use this requirements analysis for software projects across various domains, as it parses user input and creates structured markdown files suitable for design and testing teams.

The best way to resolve ambiguities in project scope is through targeted clarifying questions that identify missing constraints, actors, and functionalities before generating the final requirements document.

The generated functional requirements documents are output in structured markdown format, utilizing scripting and markdown processing libraries to ensure consistency and reproducibility.

Automated FRD generation asks clarifying questions to resolve missing information in scope, actors, and constraints, ensuring the final markdown documentation is comprehensive and actionable.