requirements-engineering

Transform business analysis documents into structured requirements by converting them into epics, features, and tech-agnostic success criteria. This ensures clear communication and provides a solid foundation for project development and subsequent architecture phases.

Generate handoff documentation for architects by extracting necessary information from the business analysis and structuring it into formal requirements. This provides architects with the essential details needed for further development and design.

Requirements engineering maintains a single source of truth for project status and artifact relations in the backlog. It preserves the hierarchical relationships between features and epics throughout the transformation process.

Yes, you can use a markdown file as input for defining project scope and prioritizing features. The skill handles various input formats, allowing you to directly process business analysis documents like 'BA-PROJECT.md'.

No, you do not need tech-specific success criteria when converting business analyses. The skill focuses on producing tech-agnostic success criteria to ensure the requirements remain flexible for the architecture phase.

The primary limitation is that the skill focuses purely on requirements transformation and handoff documentation. It does not perform architectural design, serving strictly as the bridge between business analysis and the architecture phase.