A quality-assurance test plan for a sprint or feature. It defines what to test, how to test it, which devices to use, what automated and manual checks are needed, and what counts as approval.

Use it before sprint kickoff or when starting a major feature to plan logic, integration, visual, user-interface, and configuration checks.

It turns requirements and user stories into an agreed testing plan before implementation begins.

qa-plan — Skill for Claude Code by cenconq25

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add cenconq25/claude-code-app-studio --skill qa-plan

Clone the repo

git clone --depth 1 https://github.com/cenconq25/claude-code-app-studio

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/qa-plan/github.svg)](https://agentmods.dev/skills/cenconq25/claude-code-app-studio/qa-plan)

Your own site

<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/qa-plan"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/qa-plan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/qa-plan"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/qa-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,589 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00069	$0.01589
Opus 5	$0.00034	$0.00794
Sonnet 5	$0.00014	$0.00318
Haiku 4.5	$0.00007	$0.00159

Measured 5d ago against content hash 67ed9020e9a1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

qa-plan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/qa-plan/SKILL.md · 227 lines

How it starts

The opening of the file, as written. The whole thing — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.

QA Plan

The contract that says: for this scope, here is what will be tested, how, on which devices, and what defines done. Authored once at sprint start and referenced by every QA action that follows.

Phase 1: Resolve the Scope

Parse the argument:

sprint-NN -> read production/sprints/sprint-NN/ and every story inside.
feature: <name> -> glob stories tagged for that feature/system.
No argument -> read production/session-state/active.md for the current sprint, or ask the user.

Read each story file fully — title, ID, layer, type, acceptance criteria, dependencies.

Read related PRDs from design/prd/ to understand the feature context.

Confirm scope and story count with the user.

Phase 2: Classify Each Story

For every story, assign a Test Type:

Logic — pure functions, formulas, state machines, validation, pricing math.
Integration — multi-module flows (e.g., sign-up triggers email triggers analytics event).
Visual/Feel — animation, motion, haptics, transitions.
UI — screens, navigation, forms, lists.
Config/Data — pricing, feature flags, remote config, copy.

The default mapping when ambiguous:

Story touches a screen file -> UI.
Story touches an animation/motion module -> Visual/Feel.
Story changes pricing/copy/flags only -> Config/Data.
Story implements a calculation or validator -> Logic.
Story crosses two modules with side effects -> Integration.

Surface ambiguous classifications via AskUserQuestion before continuing.

Phase 3: Determine Required Evidence

Per Type, the evidence requirement:

Type	Required evidence	Location
Logic	Unit test, must pass in CI	`tests/unit/[module]/`
Integration	Integration test or documented manual flow	`tests/integration/[module]/`
Visual/Feel	Screenshot or screen recording + lead sign-off	`production/qa/evidence/`
UI	Walkthrough doc OR Detox/Maestro/XCUITest/Espresso flow	`production/qa/evidence/` or `tests/e2e/`
Config/Data	Smoke check pass	`production/qa/smoke-[date].md`

Read the full file on GitHub · 227 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

5d ago First seen · 227 lines · 69 tokens per session scan A 67ed9020e9a1

Subscribe to this mod's changes

qa-plan is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 69 tokens to every session and 1,589 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

qa-plan