spec-manual-test

Generate manual-test documentation from spec artifacts into spec/manual-tests.

Updated Feb 27, 2025

Search Tags:#documentation #specification #qa #scenario #test-cases #manual-testing

Ready to run

npx skills add https://github.com/tuanemuy/dotfiles --skill spec-manual-test

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-manual-test
Source: https://github.com/tuanemuy/dotfiles/tree/main/config/claude/skills/spec-manual-test
Command: npx skills add https://github.com/tuanemuy/dotfiles --skill spec-manual-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual-test documentation is time-consuming to produce and risks diverging from design specifications. This Skill automates turning spec artifacts into clear, executable manual test guides that mirror user flows and validation steps.

Core Features & Use Cases

Scenario-driven test document generation from spec/scenario and spec/pages to ensure coverage of user journeys.
Alignment with spec structure (spec/scenario, spec/pages, spec/usecases, spec/testcases) to keep terminology consistent for developers and QA.
Output generation for: spec/manual-tests/index.md and spec/manual-tests/{scenario-category}.md, plus a guided review file under spec/manual-tests/review/.

Quick Start

Run the manual-test generator on the spec directory to produce the index and per-category documents.

Frequently Asked Questions about spec-manual-test

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

FAQPage Schema

How do I generate manual test documentation from software specifications?▼

Generate manual test documentation by processing spec artifacts from spec/scenario, spec/pages, and spec/usecases to produce human-readable test guides. This directly mirrors user flows and validation steps to keep QA documentation consistent with design specs.

What is the best way to keep QA test cases aligned with design specifications?▼

Align QA test cases with design specs by deriving test documents directly from the spec structure, including spec/scenario, spec/pages, and spec/usecases. This integration maintains consistent terminology for developers and QA, preventing documentation divergence.

How do I turn user scenarios and use cases into executable manual test guides?▼

Turn user scenarios and use cases into manual test guides by automating extraction of spec-derived inputs from spec/scenario and spec/usecases. This generates categorized output files under spec/manual-tests for ready-to-run QA validation.

Do I need existing test cases to generate scenario-driven manual test documents?▼

Existing test cases are not strictly required, as generation applies to specs in spec/scenario, spec/pages, and spec/usecases. However, integrating spec/testcases alongside these artifacts ensures comprehensive coverage of user journeys in the final output.

What file structure does automated manual test generation output produce?▼

Automated manual test generation outputs an index file at spec/manual-tests/index.md, per-category documents at spec/manual-tests/{scenario-category}.md, and a guided review file under spec/manual-tests/review/, plus a reference at references/test-doc-guide.md.