How do I install the Sparq:generate Manual skill?

Run npx skillmds@latest add stukh/sparq-generate-manual in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sparq:generate Manual safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sparq:generate Manual?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sparq:generate Manual free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sparq:generate Manual?

STUkh (@stukh) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sparq:generate Manual by stukh — Agent Skill

Name: Sparq:generate Manual
Author: STUkh

Sparq:generate Manual

Generate comprehensive manual test cases from requirements. Covers happy path, validation, security, edge cases, and accessibility. Outputs markdown and TMS-importable formats. Use when: (1) creating manual test cases, (2) building QA checklist, (3) preparing test plan for a feature, (4) generating TMS-importable test cases.

STUkh Updated Sep 17, 2026

File contents

Generate Manual Test Cases

Config, version check, and pattern rules per claude/rules/skills.md preamble.

Workflow

If no .sparq/requirements/REQ-{feature}.md exists, run /sparq:analyze first
CHECKPOINT -- Propose test plan: categories with case counts, priority distribution (P1/P2/P3/P4), total cases, out-of-scope items. Wait for approval.
CHECKPOINT -- Delegate to sparq-manual-test-writer agent with delegation context:
- Requirements document path and parsed content
- E2E Infrastructure Summary from config (existing page objects, components, fixtures, specs)
- Tech stack info (project.componentFileExtensions)
- Output format preference from config (outputs.testCases.format)
- Use preferences.locatorPriority from config for selector strategy when suggesting selectors in test cases For >30 tests: split into parallel batches per parallel-execution.md Pattern 2 (pre-assign TC ID ranges, launch parallel Task agents). Check project e2e structure for existing test infrastructure (page objects, component objects); flag in 'Automation Status' field. Present cases for review. Wait for confirmation.
Optionally export to TMS via /sparq:export

Chain: requirements-analyst (if needed) -> manual-test-writer -> export (optional)

Optional support: sparq-manual-test-writer agent handles generation. For complex features, the orchestrator may also involve sparq-automation-engineer for automation feasibility assessment.

Test Categories

5 canonical categories (HP, VE, SEC, EC, A11Y) -- see data-model.md "Test Category Naming" for mapping and test-generation-patterns.md for per-category checklists.

Output Files

.sparq/test-cases/TC-{feature}-manual.md -- format per .claude/templates/sparq-test-case.md
TMS export file per tms-abstraction.md (.xml for TestRail, .json for Qase/local)
.sparq/coverage/coverage-matrix.md -- format per .claude/templates/sparq-coverage-matrix.md

References

.claude/skills/sparq-shared/references/test-generation-patterns.md, tms-abstraction.md
.claude/skills/sparq-shared/references/data-model.md
.claude/skills/sparq-shared/references/parallel-execution.md

Usage

/sparq:generate-manual

Examples:

"Generate manual test cases for EP-142"
"Create QA test plan for the checkout feature"
"Build manual test cases from Confluence spec at https://..."

Example

/sparq:generate-manual EP-14
-> finds REQ-login.md -> proposes plan (26 cases across 5 categories, P1-P4)
-> CHECKPOINT: approve plan -> delegates to manual-test-writer with E2E infrastructure summary
-> generates test cases with automation status flags
-> outputs: TC-login-manual.md, TMS export, coverage-matrix.md

---name: sparq-generate-manualdescription: Generate comprehensive manual test cases from requirements. Covers happy path, validation, security, edge cases, and accessibility. Outputs markdown and TMS-importable formats. Use when: (1) creating manual test cases, (2) building QA checklist, (3) preparing test plan for a feature, (4) generating TMS-importable test cases.---# Generate Manual Test CasesConfig, version check, and pattern rules per `claude/rules/skills.md` preamble.## Workflow1. If no `.sparq/requirements/REQ-{feature}.md` exists, run `/sparq:analyze` first2. **CHECKPOINT** -- Propose test plan: categories with case counts, priority distribution (P1/P2/P3/P4), total cases, out-of-scope items. **Wait for approval.**3. **CHECKPOINT** -- Delegate to `sparq-manual-test-writer` agent with delegation context: - Requirements document path and parsed content - E2E Infrastructure Summary from config (existing page objects, components, fixtures, specs) - Tech stack info (`project.componentFileExtensions`) - Output format preference from config (`outputs.testCases.format`) - Use `preferences.locatorPriority` from config for selector strategy when suggesting selectors in test cases For >30 tests: split into parallel batches per `parallel-execution.md` Pattern 2 (pre-assign TC ID ranges, launch parallel Task agents). Check project e2e structure for existing test infrastructure (page objects, component objects); flag in 'Automation Status' field. Present cases for review. **Wait for confirmation.**4. Optionally export to TMS via `/sparq:export`**Chain**: requirements-analyst (if needed) -> manual-test-writer -> export (optional)**Optional support**: `sparq-manual-test-writer` agent handles generation. For complex features, the orchestrator may also involve `sparq-automation-engineer` for automation feasibility assessment.## Test Categories5 canonical categories (HP, VE, SEC, EC, A11Y) -- see `data-model.md` "Test Category Naming" for mapping and `test-generation-patterns.md` for per-category checklists.## Output Files- `.sparq/test-cases/TC-{feature}-manual.md` -- format per `.claude/templates/sparq-test-case.md`- TMS export file per `tms-abstraction.md` (.xml for TestRail, .json for Qase/local)- `.sparq/coverage/coverage-matrix.md` -- format per `.claude/templates/sparq-coverage-matrix.md`<done_criteria>1. `sparq.config.json` read and validated; output format preference and TMS config resolved2. Manual test cases written to `.sparq/test-cases/TC-{feature}-manual.md` with unique `TC-{feature}-{ABBR}-{NNN}` IDs3. All 5 test categories represented (HP/VE/SEC/EC/A11Y) with per-category case counts matching the approved plan4. Every test case includes traceability to at least one REQ ID from `.sparq/requirements/REQ-{feature}.md`5. TMS export file generated (`.xml` for TestRail, `.json` for Qase/local) when `outputs.tms` is configured, or export explicitly offered to user</done_criteria>## References- `.claude/skills/sparq-shared/references/test-generation-patterns.md`, `tms-abstraction.md`- `.claude/skills/sparq-shared/references/data-model.md`- `.claude/skills/sparq-shared/references/parallel-execution.md`## Usage```/sparq:generate-manual```Examples:- `"Generate manual test cases for EP-142"`- `"Create QA test plan for the checkout feature"`- `"Build manual test cases from Confluence spec at https://..."`## Example```/sparq:generate-manual EP-14-> finds REQ-login.md -> proposes plan (26 cases across 5 categories, P1-P4)-> CHECKPOINT: approve plan -> delegates to manual-test-writer with E2E infrastructure summary-> generates test cases with automation status flags-> outputs: TC-login-manual.md, TMS export, coverage-matrix.md```

Frequently asked questions