Adlc Qa
Produce ADLC QA artifacts such as change summaries, test plans, and manual test cases.
Install
$ agentstack add skill-davidvictor-adlc-skills-adlc-qa ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
ADLC QA
Use this when a feature or fix needs explicit manual QA beyond automated checks.
Modes
change-summary: summarize the actual diff and user-visible behavior.test-plan: define coverage areas, environments, risks, and pass criteria.test-cases: write concrete manual test cases.
Process
- Resolve effective ADLC paths from
.adlc/config.yaml; useadlc resolve-configwhen the CLI is available. - Read the active plan, diff, verification output, review output, rules, and relevant docs.
- Write QA artifacts under the configured QA path.
- Keep QA tied to actual behavior and acceptance criteria.
- Mark blocked or untestable cases explicitly.
- Do not change implementation code from this skill.
Output
Report QA artifact paths, coverage gaps, blocked cases, and whether the work is ready for adlc-review or adlc-commit.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: davidvictor
- Source: davidvictor/adlc-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.