solo-qa-scenario-builder

Generates structured QA test scenarios from feature specs and wireframes.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/cjrain-12505614/solo-forge-marketplace --skill solo-qa-scenario-builder-cjrain-12505614
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: solo-qa-scenario-builder
Source: https://github.com/cjrain-12505614/solo-forge-marketplace/tree/main/solo-forge-v0.6.0/skills/solo-qa-scenario-builder
Command: npx skills add https://github.com/cjrain-12505614/solo-forge-marketplace --skill solo-qa-scenario-builder-cjrain-12505614

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing comprehensive QA test scenarios manually from feature specifications is time-consuming and often misses edge cases, leaving acceptance criteria untested before release. ## Core Features & Use Cases - Systematic Test Case Generation: Creates test cases covering both happy paths and exception cases (validation errors, network failures, duplicates) with standardized TC IDs like TC-AUTH-001. - Coverage Matrix Mapping: Links every acceptance criterion from the feature spec to at least one test case and reports overall coverage percentage. - Structured Output Templates: Produces Markdown scenario documents with preconditions, step-by-step expected results, priority levels (P1-P4), and test result logs saved to docs/05_검증/. - Use Case: A solo developer finishing an authentication feature asks for test scenarios; the skill reads feature_spec_auth_v1.0.md and generates qa_scenario_auth_v1.0.md with cases for signup, duplicate email, password rules, and network errors. ## Quick Start Ask the assistant to create QA test scenarios for the signup feature based on the existing feature specification document.

Frequently Asked Questions about solo-qa-scenario-builder

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

FAQPage Schema
How do I generate QA test scenarios from a feature specification?▼

Provide the feature spec document containing acceptance criteria and request test scenario generation. The skill produces a Markdown file with test cases for each AC, covering normal flows and exception cases like validation errors and network failures.

What test case ID format does this QA scenario generator use?▼

Test cases use the format TC-{feature code}-{sequence}, such as TC-AUTH-001 for authentication or TC-PAYMENT-002 for payments. Feature codes are mapped from functional areas like AUTH, USER, ORDER, and NOTIF.

Can QA scenarios be exported to Google Sheets instead of Markdown?▼

Yes, for large projects the output can be formatted for Google Sheets with columns for TC ID, feature group, scenario name, priority, preconditions, expected results, actual results, status, and notes.

How does the skill ensure test coverage of acceptance criteria?▼

It builds a coverage matrix mapping each acceptance criterion ID from the feature spec to its related test cases, then reports the overall coverage percentage so gaps are visible before test execution.

Where are the generated QA scenario files saved?▼

Scenario documents are saved in the docs/05_검증/ folder using the naming pattern qa_scenario_{feature}_{version}.md, alongside test result logs and issue logs.