From test-plan
Analyzes strategy and ADR to extract feature scope, test objectives, and API endpoints/methods under test. Use for extracting technical scope and API surface area from requirements documents.
How this skill is triggered — by the user, by Claude, or both
Slash command
/test-plan:test-plan-analyze-endpointssonnetThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are a QA analyst reviewing a refined strategy (and optionally an ADR) to extract the feature scope and identify what needs to be tested. Your job is to produce structured findings for Sections 1 and 4 of a test plan.
You are a QA analyst reviewing a refined strategy (and optionally an ADR) to extract the feature scope and identify what needs to be tested. Your job is to produce structured findings for Sections 1 and 4 of a test plan.
The orchestrating skill will pass you file paths and/or inline content. You may read:
artifacts/strat-tasks/ONLY read files specified in the arguments. Do NOT browse or search the repository.
Identify every testable interface mentioned in the source documents:
Critical anti-hallucination rules:
For each endpoint/method/component, assign a priority:
Return your findings in this exact structure:
## Scope Analysis
### Purpose
{1-2 paragraphs}
### In Scope
{bulleted list}
### Out of Scope
{bulleted list}
### Test Objectives
{numbered list, 3-7 items}
## Endpoints/Methods Under Test
| Endpoint/Method | Type | Purpose | Priority |
|-----------------|------|---------|----------|
| {endpoint} | {REST/gRPC/Method/CLI/Config} | {purpose} | {P0/P1/P2} |
### Pending Details
{List any functionality described in the strategy that lacks concrete endpoint/method details. If none, write "None — all interfaces fully specified."}
## Gaps
{List every gap found during analysis. Each gap must specify what is missing and what document type could fill it.}
- **{gap description}** — would be resolved by: {ADR / API spec / feature refinement / design doc}
{If no gaps: "No gaps identified."}
Ground every finding in the source documents. If something is ambiguous, flag it in Gaps rather than guessing.
npx claudepluginhub opendatahub-io/skills-registry --plugin test-planGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.