Stats
Actions
Tags
From adlc-team
Start a QA session — check what needs testing, review spec quality, plan exploratory tests. Trigger: 'start working as QA', 'QA session', 'start QA'.
How this skill is triggered — by the user, by Claude, or both
Slash command
/adlc-team:qa-startThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<context>
Read (skip missing silently):
CLAUDE.md — project overview.sdlc/domain-context.md — business domain.sdlc/context-snapshot.md — last session state.sdlc/KNOWLEDGE.md — known patterns and gotchas# Features ready for QA
gh issue list --label "adlc:ready-for-qa" --limit 20 --json number,title,labels
# Specs needing AC quality review (draft specs)
gh issue list --label "adlc:spec-draft" --limit 10 --json number,title
# QA-failed issues needing re-test
gh issue list --label "adlc:qa-failed" --limit 10 --json number,title
# Recently completed tasks (may need spot checks)
gh issue list --label "adlc:done" --limit 10 --json number,title,updatedAt
## QA Session — [project name]
**Ready for QA testing:** [count] features
[list with feature IDs and brief descriptions]
**Specs needing AC review:** [count]
[list — QA reviews if ACs are testable before BA approves]
**Failed QA, needs re-test:** [count]
[list with last failure reason]
**Suggested next action:** [highest priority item]
Options:
If user chooses exploratory testing, generate a structured test charter:
**Feature:** [FEAT-ID]
**Time box:** [30/60 min]
**Focus area:** [specific area to explore]
**Test ideas:**
1. [scenario to try manually]
2. [edge case to verify]
3. [integration point to check]
**What to look for:** [specific symptoms of problems]
**Record findings in:** .sdlc/reviews/[FEAT-ID]-exploratory.md
npx claudepluginhub obacker/claude-code-plugins --plugin adlc-teamGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.