sparq:generate-manual

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

27|4|Updated Feb 27, 2026

Search Tags:#qa #traceability #generate #test-plans #manual-tests #tms-export

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The workflow for turning written requirements and Confluence/Jira specs into concrete manual test cases can be time-consuming and error-prone. This skill streamlines that process by generating structured manual test plans from a requirements document, ensuring coverage across critical test categories.

Core Features & Use Cases

Generate manual test cases aligned with canonical categories (HP, VE, SEC, EC, A11Y) from feature requirements.
Produce a human-ready test plan and a TMS-friendly export format for traceability.
Use case: when preparing QA for a new feature, it creates a complete baseline set of manual tests and checks.

Quick Start

Invoke /sparq:generate-manual with a feature key to start generating manual tests.

Frequently Asked Questions about sparq:generate-manual

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

FAQPage Schema

How do I generate manual test cases from Jira or Confluence feature requirements?▼

Manual test case generation from Jira or Confluence requirements involves transforming feature specs into structured test plans covering HP, VE, SEC, EC, and A11Y categories, producing human-ready artifacts for review and traceability.

What are the canonical test categories used when creating manual test plans?▼

Canonical test categories for manual test plans include HP, VE, SEC, EC, and A11Y, ensuring comprehensive coverage across critical quality dimensions and providing structured test documentation for traceability.

Can I export generated manual tests to a test management system format?▼

Yes, generated manual tests can be exported to a TMS-friendly format, providing test management system export-ready outputs alongside markdown artifacts to satisfy traceability needs and structured documentation requirements.

Does this manual test generation approach work with plain-text requirements?▼

Yes, this manual test generation approach works with plain-text requirements, transforming them into comprehensive manual test cases and structured test plans just as effectively as structured Jira or Confluence feature specifications.

What's the best way to ensure traceability when generating manual test plans?▼

The best way to ensure traceability when generating manual test plans is to produce TMS-friendly export formats that link structured test artifacts directly back to original feature requirements and specifications.

When do I need to generate manual tests instead of automated test scripts?▼

You need to generate manual tests when preparing QA for a new feature requires a complete baseline set of human-ready checks for review, rather than executable automated test scripts or code-based validation.