skills.rest
danhannah94
danhannah94COMMUNITY
Explore all skills by this author →
GitHub

csdlc-qa

Verify acceptance criteria and post QA annotations to Foundry.

Updated Apr 10, 2026
Search Tags:#qa#story#reporting#evidence#edge-cases#foundry#acceptance-criteria
One-click install
npx skills add https://github.com/danhannah94/claymore-plugins --skill csdlc-qa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: csdlc-qa
Source: https://github.com/danhannah94/claymore-plugins/tree/main/csdlc/skills/csdlc-qa
Command: npx skills add https://github.com/danhannah94/claymore-plugins --skill csdlc-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This QA skill provides a structured, post-implementation verification workflow that ensures completed stories meet their acceptance criteria, gather evidence, and remain separate from the implementation phase.

Core Features & Use Cases

  • Acceptance criteria validation: Verifies each criterion against testable results and logs pass/fail.
  • Edge-case testing & evidence capture: Tests boundary and error conditions and attaches evidence (logs, screenshots, outputs).
  • Foundry integration & reporting: Posts QA annotations to the story doc for human review and future audit.

Quick Start

Provide a complete QA report for the specified story by loading its acceptance criteria, executing verification steps, and attaching evidence.

Frequently Asked Questions about csdlc-qa

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate verification of acceptance criteria for completed software stories?▼

Automating verification of acceptance criteria involves loading criteria from the story doc, executing testable results, logging pass/fail outcomes, and capturing boundary edge-case evidence for human review.

What is the best way to collect QA evidence and edge-case notes for post-implementation testing?▼

Collecting QA evidence and edge-case notes requires testing boundary and error conditions during post-implementation QA, then attaching outputs like logs and screenshots into a structured report.

Does Foundry integration support posting QA annotations to story docs automatically?▼

Foundry integration supports posting QA annotations automatically to the story doc, providing structured pass/fail results, evidence, and edge-case notes for future audit and human review.

How do I generate a structured QA report separating implementation from verification?▼

Generating a structured QA report separate from implementation requires validating acceptance criteria, testing error conditions, and outputting pass/fail results alongside captured evidence for readiness review.

Can I validate edge cases and attach outputs for completed stories in Foundry workflows?▼

Validating edge cases and attaching outputs in Foundry workflows is supported by executing boundary condition tests, capturing logs or screenshots as evidence, and posting annotations to the story doc.

Related Skills

Explore More Software Engineering Skills→
thewind121212thewind121212

topic-creator

Ground user ideas in repo state and C3 architecture into implementable Stories.

Community
Intermediate
SeventeenthEarthSeventeenthEarth

17th-task-inspector

Inspect implementation compliance against TASK.md and produce a PASS/FAIL verdict report.

Community
Advanced
nuoyanruoshuinuoyanruoshui
47

qa-plan

Generate structured QA test plans from sprint, feature, or story requirements.

Community
Advanced
dangelesdangeles
6

completion-verifier

Verify task completion against acceptance criteria and generate a verification report.

Community
Advanced