manual-test-plans

Generates interactive HTML pages for manual QA test plans with pass/fail tracking.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/samcorl/qa-flows --skill manual-test-plans-samcorl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manual-test-plans
Source: https://github.com/samcorl/qa-flows/tree/main/skills/manual-test-plans
Command: npx skills add https://github.com/samcorl/qa-flows --skill manual-test-plans-samcorl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manual QA testing often relies on scattered spreadsheets or documents with no consistent way to track which cases passed, failed, or remain untested. This Skill turns a markdown test plan into a self-contained HTML page where a human tester can execute cases by hand and record results interactively. ## Core Features & Use Cases - Interactive HTML Test Plans: Renders each test case with a pending/pass/fail control, a sticky header with live counts, a progress bar, and per-case notes fields. - Markdown as Source of Truth: Plans are authored as markdown (interactively with Claude or by hand) under a configurable per-project directory, and HTML is always regenerated from that source. - Result Round-Trip: A "Save Results" button downloads the markdown source with each case's result annotation updated, which can be handed back to Claude to reconcile into the project. - Use Case: Ask Claude to create a manual test plan for your checkout flow, open the generated HTML in any browser, click through each case during testing, then save and return the results file for reconciliation. ## Quick Start Ask Claude to create a manual test plan for the feature you want to test, for example by saying "create test plan checkout_smoke".

Frequently Asked Questions about manual-test-plans

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

FAQPage Schema
How do I create a manual QA test plan as HTML?

Describe the feature under test and ask Claude to create a test plan. The skill drafts test cases interactively, writes a markdown source file, then generates a self-contained HTML page with pass/fail controls you open in any browser.

How do testers record pass and fail results in the generated page?

Each test case has a three-state pending/pass/fail button control plus a notes field. A sticky header shows live counts and a progress bar, and state persists in the browser's localStorage across reloads.

Does the generated test plan page need a web server?

No, the generated HTML file is fully self-contained with inline CSS and JavaScript. Opening it directly in a browser is enough, with no server, build step, or external dependencies required.

How do test results get saved back into the markdown source?

The page's Save Results button downloads the markdown source with each case's result annotation updated in place. Hand that file back to Claude, which summarizes the results and, with your confirmation, replaces the source and regenerates the HTML.

Where are test plan files stored in a project?

Both markdown sources and generated HTML live in a plans_dir you configure once per project in .claude/manual-test-plans.config.json, typically docs/manual-test-plans for checked-in plans or tmp/manual-test-plans for scratch work.

Is this the same as automated browser testing with Playwright?

No, this skill is for human-executed QA only, with no browser automation. The separate user-flows skill drives Playwright automatically; the two share no file format or configuration.