sparq:export

Publish QA artifacts to TMS providers, Jira, and Confluence.

27|4|Updated Feb 27, 2026

Search Tags:#qa #jira #confluence #export #test-management #testrail

Ready to run

npx skills add https://github.com/STUkh/sparq-assistant --skill sparq-export

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sparq:export
Source: https://github.com/STUkh/sparq-assistant/tree/main/claude/skills/sparq-export
Command: npx skills add https://github.com/STUkh/sparq-assistant --skill sparq-export

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exporting test cases to TMS (TestRail/Qase/Zephyr Scale/local), Jira, or Confluence. Use when: (1) pushing test cases to a TMS provider, (2) linking test coverage to Jira tickets, (3) publishing test plans to Confluence, (4) syncing QA artifacts with external tools.

Core Features & Use Cases

Supports multi-target exports across TMS providers, Jira, and Confluence.
Maintains traceability by writing back identifiers to local test-case frontmatter and generating coverage artifacts.
Provides per-target workflows (CREATE/UPDATE/SKIP/REMOVE) and robust fallback handling when MCP integrations are unavailable.

Quick Start

Run /sparq:export to push QA artifacts to configured targets.

Frequently Asked Questions about sparq:export

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

FAQPage Schema

How do I export test cases to TestRail or Jira?▼

Export test cases to TestRail or Jira by running the export command to push QA artifacts to configured TMS providers and Atlassian targets. It supports multi-target synchronization across test management systems and ticketing tools.

Can I sync QA artifacts to Confluence and Jira at the same time?▼

Yes, you can sync QA artifacts to Confluence and Jira simultaneously through multi-target exports. The skill applies per-target workflows like CREATE, UPDATE, SKIP, or REMOVE to manage synchronization across each destination independently.

How does test coverage traceability work when exporting to a TMS?▼

Test coverage traceability is maintained by writing back external identifiers to local test-case frontmatter and generating coverage artifacts. This links requirements to tests across TMS providers, Jira, and Confluence.

What happens if MCP integrations are unavailable during a TMS export?▼

If MCP integrations are unavailable during a TMS export, the skill applies robust fallback handling to ensure the process completes. This prevents synchronization failures when pushing test cases or coverage references.

Do I need configured targets to publish test plans to Confluence?▼

Yes, you need configured targets to publish test plans to Confluence. The skill enforces configurable outputs and per-target workflows to ensure artifacts push correctly to the specified Atlassian tools.

What's the best way to update existing test cases in Qase instead of creating duplicates?▼

To update existing test cases in Qase without creating duplicates, use the UPDATE workflow during export. The skill applies per-target workflows like CREATE, UPDATE, SKIP, or REMOVE to manage artifact synchronization.