pair-capability-design-manual-tests

Name: pair-capability-design-manual-tests
Availability: InStock
Author: Foomakers

Generate manual test suites with critical path files and READMEs.

6|Updated Aug 3, 2025

Search Tags:#testing #quality assurance #manual testing #test design #test suite #release validation

Ready to run

npx skills add https://github.com/foomakers/pair --skill pair-capability-design-manual-tests

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pair-capability-design-manual-tests
Source: https://github.com/foomakers/pair/tree/main/.claude/skills/pair-capability-design-manual-tests
Command: npx skills add https://github.com/foomakers/pair --skill pair-capability-design-manual-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of manual test suites, ensuring thorough validation of software releases by analyzing project artifacts and defining critical test paths.

Core Features & Use Cases

Automated Test Suite Generation: Designs critical path test files (CP*.md) and suite READMEs based on project scope and artifacts.
Comprehensive Coverage: Analyzes websites, CLIs, datasets, and registries to identify testable surfaces.
Use Case: Before releasing a new version of a web application, use this Skill to generate a complete manual test suite covering critical user flows, responsive design, and API interactions, ensuring all key functionalities are validated.

Quick Start

Use the pair-capability-design-manual-tests skill to generate a manual test suite for the website and CLI components.

Frequently Asked Questions about pair-capability-design-manual-tests

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

FAQPage Schema

How do I design a manual test suite for release validation?▼

Design a manual test suite for release validation by analyzing project artifacts, architecture, and deployment targets to generate critical path files and a suite README covering website, CLI, dataset, and registry components.

What is a critical path test file in manual testing?▼

A critical path test file in manual testing defines essential user flows and testable surfaces that must be validated post-release, ensuring key functionalities across websites, CLIs, datasets, and registries are thoroughly checked.

Can I generate manual tests for both website and CLI components?▼

Yes, you can generate manual tests for both website and CLI components by specifying your project scope, prompting the analysis of architecture and artifacts to identify testable surfaces across the requested components.

What's the best way to structure post-release manual test documentation?▼

The best way to structure post-release manual test documentation is to generate critical path files alongside a suite README, following established manual-testing guidelines to map out critical user flows and API interactions.

Does manual test design require analyzing deployment targets?▼

Yes, manual test design requires analyzing deployment targets because it identifies testable surfaces and defines critical test paths, ensuring the generated test suite accurately validates the specific release environment.