mcpbeat Sign in

Sprint Testing Workflow Agent Skill

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
32
files
ships runnable scripts
0
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”.

Other skills for the same job

different authors, same section of the catalogue
Webapp Testing
by anthropics
vendor ×12

Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.

6k tokens scripts
Finishing A Development Branch
by ZhanlinCui
×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

1k tokens
Test Driven Development
by w95
×7

Use when implementing any feature or bugfix, before writing implementation code

2k tokens
Systematic Debugging
by ratacat
×7

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

10k tokens scripts
Verification Before Completion
by ZhanlinCui
×6

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

1k tokens
Backtest Expert
by BaggaT236
×3

Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.

15k tokens scripts
Adaptyv
by christophacham
×3

Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.

16k tokens
Aeon
by christophacham
×3

This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.

19k tokens

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.