Sprint Testing Workflow

naodeng/sprint-testing-workflow

Use this skill when you need a sprint-based QA workflow from planning through review and retrospective; triggers include sprint testing workflow and iteration QA workflow.

9k tokens

context cost

the whole folder, loaded on every use

files

ships runnable scripts

copies elsewhere

how many repositories repackaged it

144

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/naodeng/awesome-qa-skills --skill sprint-testing-workflow

What comes with it

34 832 bytes besides the instruction

README.md

agents/openai.yaml

evals/cases/basic-success.yaml

evals/cases/edge-gates-handoff.yaml

evals/cases/edge-incomplete-input.yaml

evals/eval.yaml

output-templates/template-csv.csv

output-templates/template-excel.tsv

output-templates/template-json.json

output-templates/template-markdown.md

output-templates/template-word.md

output-templates/template-xmind.md

prompts/sprint-testing-workflow.md

reference.md

scripts/batch_convert_templates.py

scripts/convert_formats.py

scripts/convert_output_formats.py

scripts/convert_to_csv.py

scripts/convert_to_excel.py

scripts/convert_to_json.py

scripts/convert_to_markdown.py

scripts/convert_to_word.py

scripts/convert_to_xmind.py

scripts/parse_csv.py

scripts/parse_excel.py

scripts/parse_formats.py

scripts/parse_json.py

scripts/parse_markdown.py

scripts/parse_output_formats.py

scripts/parse_word.py

scripts/parse_xmind.py

The instruction itself

7 sections, as written by the author

Sprint Testing Workflow

中文版： See the corresponding Chinese skill.

When to Use

Need a sprint cadence: planning → setup → execution → regression → stabilize → review.
Need iteration gates and DoD with handoffs to type skills—not a one-off testing task.

Workflow

Read and follow prompts/sprint-testing-workflow.md (stages, gates, DoD, handoffs).
Add sprint goal, story scope, capacity, and carryover defects that change the plan.
After locating the stage, hand off by skill name per reference.md; no relative-path links to other skill internals.
If input is incomplete, draft a usable sprint test plan and mark assumptions and gaps.

Core Constraints

Own iteration phases and exit evidence; hand full artifacts to type skills.
Gates and DoD must be checkable.
On scope change, re-rank and state gate impact.
No relative-path links to other skill files.

Progressive Disclosure

Before producing output, read and follow prompts/sprint-testing-workflow.md.
For step ↔ handoff mapping: read reference.md.
For stage deep-dives: invoke the matching type skill; do not expand full artifacts here.
Templates: output-templates/.

Pre-delivery Checklist

[ ] Followed the main prompt’s output structure
[ ] Includes stage position, gate board, exit-criteria check, next skill
[ ] High-risk items have priority and Owner
[ ] Did not invent details the user did not provide
[ ] Assumptions, tradeoffs, and carryover are marked

Common Pitfalls

Do not write a day diary with no gates.
Do not dump full case bodies during planning.
Do not claim regression passed while development is still open-ended.
Do not replace exit evidence with “we tested a lot”.

How to use it

Copy the folder

Take naodeng/sprint-testing-workflow from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.