design-manual-tests

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

Generate critical path files and a suite README for manual post-release testing.

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 design-manual-tests

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design-manual-tests
Source: https://github.com/foomakers/pair/tree/main/packages/knowledge-hub/dataset/.skills/capability/design-manual-tests
Command: npx skills add https://github.com/foomakers/pair --skill 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 post-release validation by analyzing project artifacts and deployment targets. It saves significant time and effort in test case design.

Core Features & Use Cases

Automated Test Suite Generation: Creates critical path files (CP*.md) and a suite README.
Surface Discovery: Analyzes websites, CLIs, datasets, and registries to identify testable areas.
Use Case: Before releasing a new version of your CLI tool, use this Skill to automatically generate a comprehensive manual test suite covering installation, core commands, and error handling, ensuring all critical functionalities are validated.

Quick Start

Design a manual test suite for the website and CLI components of the current project.

Frequently Asked Questions about design-manual-tests

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

FAQPage Schema

How do I create a manual test suite for post-release validation?▼

To create a manual test suite for post-release validation, analyze your project artifacts, architecture, and deployment targets to generate structured critical path files (CP*.md) and a suite README covering testable areas.

What components can I cover when designing manual tests for my project?▼

When designing manual tests, you can cover website, CLI, dataset, and registry components by using automated discovery to analyze project artifacts and identify critical paths for structured test case generation.

How do I generate test cases for CLI tool releases?▼

Generate test cases for CLI tool releases by analyzing deployment targets and architecture to produce critical path files that validate installation, core commands, and error handling as part of a comprehensive manual test suite.

Does manual test suite generation work without external dependencies?▼

Yes, manual test suite generation works without external dependencies, analyzing project artifacts and deployment targets internally to produce critical path files and a suite README for release validation.

What's the best way to validate critical paths before a release?▼

The best way to validate critical paths before a release is to generate a structured manual test suite that analyzes project architecture and deployment targets, producing critical path files (CP*.md) for thorough validation.

When should I use manual testing instead of automated testing for release validation?▼

Use manual testing for release validation when you need to verify critical paths across website, CLI, dataset, and registry components through human-executable test cases generated from project artifacts and deployment targets.