Daily Testing Workflow - QA Skill Library

Why this Skill

It turns this Skill's method into a quality input that can be executed, reviewed, and reused.

Need a one-day QA cadence: morning plan, execution, defects, EOD wrap-up.
Own phases and gates; hand full cases/strategy/reports to type skills.
Prioritize by risk; gates must be checkable.
Separate confirmed facts from assumptions.
Do not turn the daily workflow into a functional-testing encyclopedia.

When to use

Use this Skill

Need a one-day QA cadence: morning plan, execution, defects, EOD wrap-up.
Need stage gates and handoffs to type skills—not a single isolated testing task.

Common pitfalls

Do not turn the daily workflow into a functional-testing encyclopedia.
Do not leave work forever “in progress” without exit criteria.
Do not hand off multiple equal primary skills at once.
Do not pretend execution succeeded on a red environment.

Input

Minimum Input

The current task scope, objective, and subject under review.

Recommended Input

Before producing output, read and follow prompts/daily-testing-workflow.md.
For step ↔ handoff skill mapping: read reference.md.
When deep-diving a stage: invoke the matching type skill (e.g. bug-reporting); do not expand full artifacts here.
When a template fits: use matching files under output-templates/.

Optional Context

Relevant code or configuration
Historical results
Logs and metrics

Output

The output follows this Skill's method and makes facts, assumptions, risks, and next steps explicit.

Judge the output value before installing

01Followed the main prompt’s output structure
02Includes today’s scope/won’t-do, gate status, priority queue, next skill
03High-risk items have explicit priority
04Did not invent details the user did not provide

View full output structure

05Assumptions and gaps are marked

How It Works

01Read and follow prompts/daily-testing-workflow.md (stages, gates, handoffs, output structure).
02Add only context that changes the result: day scope, environment, constraints, risks, carryover defects.
03After locating the stage, hand off by skill name per reference.md; no relative-path links to other skill internals.
04If input is incomplete, draft a usable day plan and mark assumptions and gaps.

Install & Quick Start

Install command / SHELL

npx skills add \
  https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-workflows/daily-testing-workflow
  -g

daily-testing-workflow.prompt

@skill daily-testing-workflow

Using the current project context, produce an actionable result following this Skill.

Additional context:
[Paste project context or requirement]

---
name: daily-testing-workflow
description: Use this skill when you need a day-by-day QA routine including planning, execution, bug reporting, and end-of-day wrap-up; triggers include daily testing workflow and daily QA routine.
---

# Daily Testing Workflow

**Chinese version：** See the corresponding Chinese skill.

## When to Use

- Need a one-day QA cadence: morning plan, execution, defects, EOD wrap-up.
- Need stage gates and handoffs to type skills—not a single isolated testing task.

## Workflow

1. Read and follow `prompts/daily-testing-workflow.md` (stages, gates, handoffs, output structure).
2. Add only context that changes the result: day scope, environment, constraints, risks, carryover defects.
3. After locating the stage, hand off by skill name per `reference.md`; no relative-path links to other skill internals.
4. If input is incomplete, draft a usable day plan and mark assumptions and gaps.

## Core Constraints

- Own phases and gates; hand full cases/strategy/reports to type skills.
- Prioritize by risk; gates must be checkable.
- Separate confirmed facts from assumptions.
- Do not invent missing details; no relative-path links to other skill files.

## Progressive Disclosure

- Before producing output, read and follow `prompts/daily-testing-workflow.md`.
- For step ↔ handoff skill mapping: read `reference.md`.
- When deep-diving a stage: invoke the matching type skill (e.g. `bug-reporting`); do not expand full artifacts here.
- When a template fits: use matching files under `output-templates/`.

## Pre-delivery Checklist

- [ ] Followed the main prompt’s output structure
- [ ] Includes today’s scope/won’t-do, gate status, priority queue, next skill
- [ ] High-risk items have explicit priority
- [ ] Did not invent details the user did not provide
- [ ] Assumptions and gaps are marked

## Common Pitfalls

- Do not turn the daily workflow into a functional-testing encyclopedia.
- Do not leave work forever “in progress” without exit criteria.
- Do not hand off multiple equal primary skills at once.
- Do not pretend execution succeeded on a red environment.