skills.rest
STUkh
STUkhCOMMUNITY
Explore all skills by this author →
GitHub

sparq:analyze

Consolidate project requirements from Jira, Confluence, Figma, and local files into a unified spec.

27|4|Updated Feb 27, 2026
Search Tags:#requirements#figma#test-generation#jira#confluence#analyze#requirements-document
One-click install
npx skills add https://github.com/STUkh/sparq-assistant --skill sparq-analyze
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sparq:analyze
Source: https://github.com/STUkh/sparq-assistant/tree/main/claude/skills/sparq-analyze
Command: npx skills add https://github.com/STUkh/sparq-assistant --skill sparq-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidate fragmented project requirements from Jira, Confluence, Figma, and local files into a single, actionable spec for testing and automation.

Core Features & Use Cases

  • Integrates inputs from Jira, Confluence, Figma, and local docs into a unified requirements document.
  • Generates structured requirements with acceptance criteria to bootstrap manual and E2E testing.
  • Supports quick iteration by triggering on Jira ticket IDs, Confluence URLs, Figma links, or plain feature descriptions.

Quick Start

Invoke this skill with a Jira ticket ID, Confluence URL, Figma link, or plain feature description to generate a consolidated requirements document.

Frequently Asked Questions about sparq:analyze

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

FAQPage Schema
How do I consolidate requirements from Jira, Confluence, and Figma into a single document?▼

Consolidating requirements from Jira, Confluence, and Figma involves triggering the skill with a ticket ID, URL, or link to merge fragmented sources into a unified requirements document with acceptance criteria.

Can I generate test cases from plain text feature descriptions?▼

Yes, you can generate structured requirements from plain text feature descriptions. The skill processes these inputs alongside Jira and Confluence data to produce structured output for test generation and automation.

What is the best way to generate E2E testing specs from fragmented project documents?▼

The best way to generate E2E testing specs from fragmented documents is to consolidate inputs from Jira, Confluence, Figma, and local files into a single actionable spec with acceptance criteria to bootstrap testing.

Does this requirements consolidation tool work with local files and Figma UI flows?▼

Yes, this requirements consolidation tool works with local files and Figma UI flows. It applies integration across Jira tickets, Confluence specs, Figma links, and local files to produce a unified requirements document.

How do I derive a feature name and acceptance criteria from a Jira ticket ID?▼

To derive a feature name and acceptance criteria from a Jira ticket ID, invoke the skill with the ID to process ticket details and generate a structured requirements document with feature name derivation.

Are there limitations when consolidating Confluence specs and Figma links for test generation?▼

Consolidating Confluence specs and Figma links for test generation is limited to producing structured output for downstream test generation, without directly executing tests or validating the UI flows within the source platforms.

Related Skills

Explore More Product & Management Skills→
javierhbrjavierhbr

extract-wisdom

Extract insights, quotes, summaries, and actionable steps from text sources.

Community
Intermediate
wangtengda0310wangtengda0310

test-case-generator

Generate structured test cases across unit, integration, and end-to-end testing.

Community
Advanced
ganeshgaxyganeshgaxy

noob-ticket-cache

Cache and reuse Jira/Confluence ticket context data with TTL-managed access.

Community
Advanced
STUkhSTUkh
27

sparq:generate-manual

Generate manual test cases from QA requirements across HP, VE, SEC, EC, and A11Y.

Community
Advanced