how-to-test

Generate QA-facing How-To-Test manuals from workspace configurations and feature artifacts.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/samykabu/sanduq --skill how-to-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: how-to-test
Source: https://github.com/samykabu/sanduq/tree/main/skills/devtools/skills/how-to-test
Command: npx skills add https://github.com/samykabu/sanduq --skill how-to-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the generation of comprehensive, development-focused How-To-Test manuals for internal QA and development teams, ensuring thorough coverage of every user case and providing necessary documentation for validation.

Core Features & Use Cases

  • Generate QA-Facing How-To-Test Manuals: Automatically produce detailed test guides for development staff.
  • Supports Multi-Project Workspaces: Handles multiple projects and aggregates manuals for each, creating a comprehensive overview.
  • User-Story-Based Sections: Manually create sections for each user story, with scenarios, preconditions, steps, and expected results.
  • Visuals & Screenshots: Embed architecture diagrams, process flow visuals, and screenshots to provide clarity and context.

Quick Start

Run the how-to-test skill on your project to generate the How-To-Test manual.

Frequently Asked Questions about how-to-test

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

FAQPage Schema
How do I generate QA documentation for internal development teams?

You generate QA documentation by scanning workspace configurations and feature artifacts to automatically produce How-To-Test manuals featuring user-story sections, scenarios, preconditions, and expected results for development and QA teams.

What is the best way to create manual test cases from feature artifacts?

Creating manual test cases is best handled by scanning feature artifacts to automatically structure user-story-based sections with scenarios, preconditions, steps, and expected validation results for QA teams.

Do I need Python to generate How-To-Test manuals for my projects?

Yes, Python is required to execute the manual generation process, which also relies on various tools to generate architecture diagrams and capture screenshots for visual clarity in the documentation.

Can I use a single tool to generate test guides for a multi-project workspace?

Yes, you can generate test guides for a multi-project workspace by scanning and aggregating configurations across projects to create a comprehensive overview with individual How-To-Test manuals for each feature.

How do I include architecture diagrams and screenshots in my QA testing documentation?

You include architecture diagrams and screenshots by using a generation process that relies on various external tools to capture visuals and embed them directly into the QA documentation for added context.