manual-testing-protocol

Coordinate manual testing requests with structured plans and handoff messages.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/leandro-br-dev/charhub --skill manual-testing-protocol
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manual-testing-protocol
Source: https://github.com/leandro-br-dev/charhub/tree/main/docs/agents/coder/skills/orchestration/manual-testing-protocol
Command: npx skills add https://github.com/leandro-br-dev/charhub --skill manual-testing-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate manual testing efforts by guiding users through validated test plans and collecting structured feedback after the server stabilizes.

Core Features & Use Cases

  • Provides a repeatable workflow for requesting manual testing.
  • Generates testing instructions, access details, and validation templates.
  • Supports handoff from manual testing to automated validation and documentation.

Quick Start

Explain the testing plan and present structured prompts to the user.

Frequently Asked Questions about manual-testing-protocol

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

FAQPage Schema
How do I coordinate manual testing workflows after server stability is verified?

A manual testing protocol structures feature-verification by providing explicit testing steps, formatted templates, and handoff messages. It aligns with the examiner's workflow to collect structured feedback after server stability is verified.

How do I create a structured manual testing plan for feature verification?

Generate a manual testing plan by presenting structured prompts and formatted templates to the user. This coordinates feature-verification through explicit steps, access details, and user-facing testing guidance.

What is the best way to hand off manual testing results to automated validation?

Hand off manual testing to automated validation by collecting structured feedback through formatted templates. The protocol aligns handoff messages with the examiner's workflow to ensure smooth downstream automation.

When do I need a formal testing protocol for QA workflows?

A formal testing protocol is needed for QA workflows when coordinating manual feature-verification after server stability is verified. It provides a repeatable workflow with testing instructions, access details, and validation templates.

Does manual testing coordination require any specific dependencies or components?

Manual testing coordination requires no external dependencies or components. The protocol operates as a standalone workflow using formatted testing templates and handoff messages to guide feature-verification.

Can I use this manual testing protocol before automated testing and documentation?

Apply this manual testing protocol after server stability is verified and before automated testing and documentation. It coordinates feature-verification, generates instructions, and prepares handoff for downstream tasks.