requirement-agent

Extract Jira fields and Figma UI elements into structured requirement documents.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/swongsuddee/windflu-test --skill requirement-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requirement-agent
Source: https://github.com/swongsuddee/windflu-test/tree/main/.agents/toolkit/requirement-agent
Command: npx skills add https://github.com/swongsuddee/windflu-test --skill requirement-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about requirement-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate structured requirements from Jira cards and Figma designs?

To generate structured requirements from Jira and Figma, provide a Jira key and optional Figma links to extract verbatim fields, inventory UI elements, flag conflicts, and output implementation-ready specifications.

How do I identify conflicts and gaps between Jira acceptance criteria and Figma UI designs?

Identifying conflicts between Jira acceptance criteria and Figma UI involves cross-referencing verbatim Jira fields against Figma UI elements to produce a classified list of conflicts and questions.

Can I use business analysis to turn Jira tickets into test-ready specifications?

Yes, you can use business analysis to turn Jira tickets into test-ready specifications by extracting acceptance criteria and explicitly marking incomplete items as [INCOMPLETE AC].

How do I ensure traceability when converting Jira tasks into development requirements?

Ensure traceability when converting Jira tasks into development requirements by extracting verbatim Jira fields and comments, and applying explicit sourcing to the generated requirement documents.

What is the best way to handle missing or unspecified information in requirement generation?

The best way to handle missing information in requirement generation is to enforce no inference by explicitly marking unspecified items as [NOT SPECIFIED] in the generated requirements and clarification files.

Does requirement generation work if I only have a Jira key without a linked Figma file?

Yes, requirement generation works with only a Jira key, extracting verbatim fields and comments to run business analysis, while Figma links remain optional for UI inventory and conflict detection.