Test verification strategy
Skill jukrap/ai-agent-playbook/skills/delivery/test-verification-strategy
Reusable AI agent skills, project templates, and guardrails for safer software maintenance and delivery.
npx -y skills add jukrap/ai-agent-playbook --skill test-verification-strategyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when planning, reviewing, or repairing verification strategy, test scope, contract/manual checks, coverage gaps, risk-based selection, or release confidence.
SKILL.md
1.0 KB, 165 tokens by cl100k_base, as published. Nobody here has run it
Test Verification Strategy
Use this as the primary delivery skill for choosing and defending verification coverage.
Workflow
- Identify the change risk, users, code paths, data shape, external systems, and release or rollback pressure.
- Map risk to the cheapest reliable checks: static, unit, integration, contract, E2E, visual, migration, smoke, manual, or monitor-based.
- Separate required checks from nice-to-have checks, and name what remains unverified.
- Verify with project-defined commands first, then record actual checks and remaining risk in the handoff.
Reference
Read references/risk-based-test-plan.md for test scope, blast radius, and release confidence planning.
Read references/verification-matrix.md for mapping change types to concrete verification commands and evidence.