qa-plan

Generate a QA test plan for a sprint or feature. Reads GDDs and story files, classifies stories by test type (Logic/Integration/Visual/UI), and produces a structured test plan covering automated tests required, manual test cases, smoke test scope, and playtest sign-off requirements. Run before sprint begins or when starting a major feature.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a highly actionable, clearly sequenced workflow with strong validation checkpoints and no conceptual padding. Its main weakness is progressive disclosure: it is a self-contained monolith with no offloaded reference files despite a large embedded template.

Suggestions

Move the Phase 4 QA-plan markdown template into a reference file (e.g. references/qa-plan-template.md) and reference it one level deep, so SKILL.md stays an overview and the template earns progressive-disclosure credit.

Trim the opening two paragraphs, which restate the frontmatter description, plus the 'post-mortem' aphorism, to tighten conciseness further.

Consider extracting the Phase 3 classification table into a reference if the skill grows, keeping the inline version as a summary pointer.

Dimension	Reasoning	Score
Conciseness	Procedural and specific throughout, with no explanation of concepts Claude already knows (it never defines unit tests, GDDs, or smoke testing); the opening recap and 'post-mortem' aphorism are mildly trimmable but the dominant character is lean and competence-assuming.	3 / 3
Actionability	Provides concrete file paths, exact argument forms, a copy-ready markdown template, exact AskUserQuestion wording, named edge-case categories, and a Definition-of-Done checklist — fully executable guidance.	3 / 3
Workflow Clarity	Five sequenced phases with explicit validation checkpoints (missing files noted as MISSING, missing GDD/Edge Cases flagged without blocking, classification summary shown before plan generation, write gated on explicit approval) and clear feedback loops.	3 / 3
Progressive Disclosure	No bundle files exist and the skill is a single ~270-line monolithic document; the large Phase 4 template is content that could live in a separate reference file but is kept inline, matching the score-2 'content that should be separate is inline' anchor rather than well-signaled one-level references.	2 / 3
	Total	11 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, complete, and distinctive: it names concrete actions, explicit when-triggers, and a clear niche with natural trigger terms. It is a strong, well-calibrated skill description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — reads GDDs and story files, classifies stories by test type (Logic/Integration/Visual/UI), and produces a structured plan covering automated tests, manual cases, smoke scope, and playtest sign-off — matching the score-3 anchor for multiple specific actions.	3 / 3
Completeness	Explicitly answers both what (generate/classify/produce the 4-part plan) and when ('Run before sprint begins or when starting a major feature'); trigger guidance is present, so it is not capped at 2.	3 / 3
Trigger Term Quality	Uses natural terms a game-dev user would say ('QA test plan', 'sprint', 'feature', 'GDDs', 'story files') and gives an explicit when-trigger ('Run before sprint begins or when starting a major feature'), giving good coverage rather than just jargon.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (game-dev QA planning for sprints/features) with distinct triggers unlikely to fire for unrelated skills; uses imperative third-person voice with no first/second-person phrasing.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: Donchitos/Claude-Code-Game-Studios
Path: .claude/skills/qa-plan/SKILL.md
Commit: 984023d

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.