Complete Problem-Based Software Requirements Specification methodology following Gorski & Stadzisz research. Use when you need to perform requirements engineering from business problems to...

Conducts comprehensive requirements review including completeness validation, clarity assessment, consistency checking, testability evaluation, and standards compliance. Produces detailed review...

Transform BUSINESS-CASE.md into formal software requirements. Use when user has completed /create-business-case and needs SRS or User Stories documentation.

Transform requirements into software architecture documentation. Use when user has requirements specs, user stories, or business cases and needs design documents, architecture documentation, or...

Use when starting a new project, justifying an investment, or when a research document exists but no formal business case. Triggers include "create business case", "write BRD", "business...

Guides comprehensive requirements gathering and analysis including stakeholder interviews, user story creation, use case documentation, acceptance criteria, requirements prioritization, and...