business-analyst

Execute complete business analysis workflow. Auto-detects greenfield vs brownfield and runs appropriate analysis combining codebase analysis, stakeholder interviews, and documentation.

Execute business analysis for an existing codebase. Reverse-engineers requirements from code, identifies gaps, and gathers change requirements from stakeholders.

Generate IEEE 830 compliant Software Requirements Specification document from gathered requirements.

Execute business analysis for a new project. Focuses on stakeholder interviews, scope definition, and requirements gathering from scratch.

Start interactive requirements gathering interview session. Uses structured templates with adaptive follow-ups based on stakeholder responses.

Codebase analysis specialist for reverse-engineering requirements from existing code. Use when analyzing brownfield projects, understanding existing systems, or extracting business logic from code.

Senior Business Analyst for requirements gathering, classification, and prioritization. Use when conducting requirements analysis, stakeholder management, or creating requirements documentation.

SRS document generation specialist for creating IEEE 830 compliant Software Requirements Specification documents. Use when compiling gathered requirements into formal documentation.

Stakeholder interview specialist for structured and adaptive requirements gathering. Use when conducting detailed interviews, gathering user perspectives, or exploring specific requirement areas in depth.

Validation and quality assurance specialist for verifying requirements artifacts. Use to validate SRS documents, check requirement quality, ensure completeness, and provide feedback on work products.

Techniques for analyzing existing codebases to reverse-engineer requirements and understand business logic. Use when conducting brownfield analysis or understanding existing system capabilities.

Requirements gathering and elicitation techniques for business analysis. Use when conducting stakeholder interviews, gathering functional/non-functional requirements, or identifying gaps in requirements.

Software Requirements Specification documentation following IEEE 830 standard. Use when generating formal SRS documents or compiling gathered requirements into structured documentation.

Technical analysis capabilities for APIs, data models, integrations, and security requirements. Use when analyzing technical aspects of systems or documenting technical requirements.

1 hook across 1 event