What problem does it solve? Running a project's manual test suite by hand after each release is slow, inconsistent, and hard to audit. This Skill automates the execution of critical-path test cases against released artifacts (websites, CLI packages, registries) and produces a standardized, evidence-backed report. ## Core Features & Use Cases - Automated Suite Execution: Discovers CP*.md critical path files, resolves variables like version and base URL, and runs each test case with PASS/FAIL/BLOCKED verdicts. - Adaptive Tooling: Selects the best available tool per action (agent-browser, Playwright MCP, curl, Bash) and gracefully degrades when tools or network access are missing. - Structured Reporting: Generates a report from the manual-test-report template with per-CP summaries, failure evidence, and an overall PASS/FAIL result stored under .tmp/manual-test-reports/. - Use Case: After publishing release v1.0.1 of your CLI, invoke this Skill to run all P0 blocker tests against the published package and website, then attach the generated report to your release review. ## Quick Start Run the manual test suite in the qa directory against version 1.0.1 and generate the execution report.