Run any Skill in Manus with one click

generating-qa-scenarios

Stars2

Forks0

UpdatedMay 25, 2026 at 15:35

Generates conversational user evaluation scenarios and test case checklists for software flows or user journeys. Use when a user asks to create a testing scenario, QA checklist, or evaluation questions for a feature. Don't use for unit testing or writing automated test code.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

stenalpjolly

stenalpjolly/llm-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

3 files

SKILL.md

readonly

name	generating-qa-scenarios
description	Generates conversational user evaluation scenarios and test case checklists for software flows or user journeys. Use when a user asks to create a testing scenario, QA checklist, or evaluation questions for a feature. Don't use for unit testing or writing automated test code.

Generating QA Scenarios

Create conversational, realistic evaluation scenarios that walk testers through a software flow and ask them to verify specific actions, edge cases, fallback mechanisms, and access controls.

Guidelines for Generating Scenarios

Format: Present the scenario as a conversational checklist starting with a prompt like "Were you able to do the following:".
Coverage: Ensure the generated checklist comprehensively covers various aspects of the user journey:
- Happy Path: Standard core user actions (e.g., selection, creation, configuration).
- Automated/Complex Features: Verifying system-generated outputs or complex logic (note that users should watch for inaccuracies).
- Manual Fallbacks: Ensuring manual overrides or basic inputs work if automation/complexity fails.
- Support & Context: Interacting with support/collaborators, maintaining context, and providing external validation (e.g., sharing artifacts, links, or screens).
- Submissions/Completions: The final state or handoff to conclude the flow.
- Negative Testing & Access Controls: Explicitly verifying things the user should not see or do (e.g., verifying restricted data is hidden from regular users).
Tone: Conversational, direct, and pragmatic.

Execution Workflow

Analyze the requested feature, system, or user flow.
Map out the key actions, automated touchpoints, fallback elements, and access control boundaries for that specific system.
Draft the scenario mirroring the tone and structure found in references/example-scenario.md.
Adapt the template placeholders to fit the exact domain requested.
Output the final checklist directly to the user.

References

See references/example-scenario.md for the tone and structural pacing.

More from this repository

same repository

generating-mermaid-diagrams

stenalpjolly/llm-skills

Generates syntax-valid, render-safe Mermaid.js diagrams (flowcharts, sequence diagrams, state diagrams, ERDs, Gantt charts). Use when a user asks to draw, visualize, map out, or document systems, workflows, API sequences, database schemas, or architectures. Don't use for generic markdown tables, text-based descriptions, or non-visual data serialization.

2026-07-072

refining-feature-requests

stenalpjolly/llm-skills

Converts vague feature requests into structured product requirements (PRDs) and sprint-ready user stories. Use when scoping and planning a feature in a Product Manager or Scrum Master capacity. Don't use to write or modify application code.

2026-07-032

updating-readme

stenalpjolly/llm-skills

Standardizes how agents update and manage README.md files, adopting the Deep Insight/Strands SDK documentation style. Use when creating a new README from scratch, improving an existing README, or converting technical docs to user-friendly formats. When creating or editing Mermaid diagrams in the README, load and use the `generating-mermaid-diagrams` skill. Don't use for API-only documentation or internal technical specs.

2026-06-302

orchestrating-subagents

stenalpjolly/llm-skills

Orchestrates specialized subagents in parallel to keep the main thread idle and maximize concurrency. Use when a task can be decomposed into independent subtasks (such as concurrent code changes, parallel research, or separate validation steps), when a task is long-running and the parent thread should remain idle while waiting, or when interactive input is needed to refine features. Don't use for simple sequential tasks, single-file edits that cannot be parallelized, or when subagent support is not available in the workspace.

2026-06-252

applying-marketing-web-standards

stenalpjolly/llm-skills

Provides guidelines, visual specs, and accessibility rules for Google-branded marketing websites. Use when building or modifying web pages, landing pages, or components (such as buttons, forms, carousels, or chips) to ensure they conform to Google's layout, design, accessibility, and legal standards. Don't use for mobile native app development, generic backend service design, or premium creative visual styling (micro-animations, artistic designs)—use `designing-tasteful-frontends` for that.

2026-06-252

code-reviewer

stenalpjolly/llm-skills

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

2026-06-252

name	generating-qa-scenarios
description	Generates conversational user evaluation scenarios and test case checklists for software flows or user journeys. Use when a user asks to create a testing scenario, QA checklist, or evaluation questions for a feature. Don't use for unit testing or writing automated test code.

Generating QA Scenarios

Create conversational, realistic evaluation scenarios that walk testers through a software flow and ask them to verify specific actions, edge cases, fallback mechanisms, and access controls.

Guidelines for Generating Scenarios

Format: Present the scenario as a conversational checklist starting with a prompt like "Were you able to do the following:".
Coverage: Ensure the generated checklist comprehensively covers various aspects of the user journey:
- Happy Path: Standard core user actions (e.g., selection, creation, configuration).
- Automated/Complex Features: Verifying system-generated outputs or complex logic (note that users should watch for inaccuracies).
- Manual Fallbacks: Ensuring manual overrides or basic inputs work if automation/complexity fails.
- Support & Context: Interacting with support/collaborators, maintaining context, and providing external validation (e.g., sharing artifacts, links, or screens).
- Submissions/Completions: The final state or handoff to conclude the flow.
- Negative Testing & Access Controls: Explicitly verifying things the user should not see or do (e.g., verifying restricted data is hidden from regular users).
Tone: Conversational, direct, and pragmatic.

Execution Workflow

Analyze the requested feature, system, or user flow.
Map out the key actions, automated touchpoints, fallback elements, and access control boundaries for that specific system.
Draft the scenario mirroring the tone and structure found in references/example-scenario.md.
Adapt the template placeholders to fit the exact domain requested.
Output the final checklist directly to the user.

References

See references/example-scenario.md for the tone and structural pacing.