← LeaderboardThe Skill Leaderboard

qa

Exercise the delivered customer journey using real runtime or browser evidence. Use for functional acceptance testing after implementation, including failure paths.

Published by suboss87 ↗suboss87/FDEOps

Try your first task

Start a fresh conversation. Replace the highlighted placeholders.

Use qa to exercise the [changed journey, user roles, and acceptance checks] in the [revision and environment], using [authorized fixtures with understood cleanup]. Run the normal journey, relevant negative/boundary cases and affected neighbors through the real interface; verify persisted downstream state and inspect browser, console, and network evidence. Return a verification receipt containing checked journeys/conditions, observed results, reproducible defects with reproduction steps and impact, limitations, blockers, and any untested roles, devices, or data conditions.

Required inputs

[changed journey, user roles, and acceptance checks]
[revision and environment]
[authorized fixtures with understood cleanup]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: qadescription: Exercise the delivered customer journey using real runtime or browser evidence. Use for functional acceptance testing after implementation, including failure paths.

qa

Purpose

Customer-journey evidence and acceptance gaps.

Before investigating or acting:

Read the task context contract.
Read the method.

Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required.

Principles

Work directly from the supplied permitted context. Standalone work does not require an engagement folder or initialization. Record filenames in the method are optional persistence destinations when no engagement is bound.
If called by @fde, reuse its current sanitized packet and scope. Do not restart setup, discovery or questions already answered.
The task context contract controls persistence and authority in both modes. Preserve unknowns and distinguish implementation, verification, deployment and acceptance.
Use the customer's repository instructions and available tools. Report a missing capability or unrun check honestly; do not claim that installing a skill provisions infrastructure.