What problem does it solve?
It converts Jira cards and linked Figma designs into structured, verbatim requirement documents while explicitly flagging conflicts and gaps so downstream teams can implement with traceability.
Core Features & Use Cases
- Verbatim requirement extraction: Pulls Jira fields and subtasks without paraphrasing, including comments and acceptance criteria.
- Figma UI inventory: Extracts frames and visible UI elements (labels, placeholders, buttons, errors, and navigation hints) and cross-references them to Jira.
- Conflict and gap analysis: Produces a classified list of C (conflicts) and Q (questions), marking missing items as [NOT SPECIFIED] and incomplete AC as [INCOMPLETE AC].
- Requirement document generation: Writes a requirements markdown file plus an always-generated clarification file for review.
Quick Start
Use the requirement-agent with a Jira key to read the card, extract any Figma designs, run business analysis for conflicts and gaps, and generate the structured requirements and clarifications.