From qa-stlc-agents
Use when organising linked manual test cases into an Azure DevOps test plan by creating requirement-based suites under static suites. Triggers on: "requirement based suite", "requirement suite", "test plan suite", "add PBI to test plan", "create suite for work item", "organise test cases in test plan". Runs AFTER manual test cases are created and linked (TestedBy) to a PBI or Bug. Selects the plan by iteration + area path and the static suite by work item type (PBI / Bugs).
How this skill is triggered — by the user, by Claude, or both
Slash command
/qa-stlc-agents:create-requirement-suitesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> **Read `AGENT-BEHAVIOR.md` before this skill.** The behavior rules there override any
Read
AGENT-BEHAVIOR.mdbefore this skill. The behavior rules there override any inference. This skill provides the step-by-step workflow only.
Use this skill when, after manual test cases have been created and linked to a PBI or
Bug (via qa-test-case-manager), the user wants those test cases organised in the Azure
DevOps Test Plan as a requirement-based suite under the correct static suite.
A requirement-based suite is bound to a requirement work item and automatically includes every test case linked to that work item (TestedBy). So creating the suite is all that is needed — the linked test cases populate it instantly. This is why the manual test cases must already be linked before this skill runs.
https://dev.azure.com/myorg) and project nameIf the org URL or project name is missing, stop and ask — do not guess.
find_test_plan_for_work_itemThe target plan is the one whose Iteration equals the work item's iteration path AND whose Area Path contains the work item's area path. The tool fetches these fields from the work item itself.
no_matching_plan → report it; do not create anything. Ask the user to create/correct the plan.multiple_matching_plans → report the candidates; do not guess. Ask which plan_id to use.The requirement suite is created under the static suite matching the work item type:
| Work item type | Parent static suite (default) |
|---|---|
| Product Backlog Item | PBI |
| Bug | Bugs |
| Epic / Feature / other | Not supported — unsupported_work_item_type |
static_suite_not_found → the named static suite does not exist in the plan. The static
suite is never auto-created. Report the available static suites and ask the user to
create the expected one, then retry.linked_test_cases_count; a count of 0 means the suite would be created empty —
surface that to the user.create_requirement_suite_for_work_item with work_item_id, organization_url,
project_name. Optionally override pbi_suite_name / bug_suite_name, or pass an
explicit plan_id to skip auto-resolution.created → report the new suite id, the parent static suite, the plan, and the linked
test case count.already_exists → idempotent hit; report the existing suite id, do not duplicate.error key → surface the message verbatim and stop.list_test_plans — inspect all plans (id, name, area_path, iteration).find_test_plan_for_work_item — resolve THE plan for a work item (iteration + area).list_test_suites — inspect a plan's suites (static + requirement) before/after creation.create_requirement_suite_for_work_item — the end-to-end action; auto-creates nothing but
the requirement suite, is idempotent, and refuses to guess on ambiguity.npx claudepluginhub qa-gentic/stlc-agents --plugin qa-stlc-agentsProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.