Agent skill

Quality Engineering Test Plan Authoring

by HoangNguyen0403 in HoangNguyen0403/agent-skills-standard

Turn acceptance criteria into an executable test plan (scenarios, seed, selector gaps) before generating E2E code.

MITAuto-check passedTesting & QA

Install Quality Engineering Test Plan Authoring

skills CLI
$ npx skills add HoangNguyen0403/agent-skills-standard --skill quality-engineering-test-plan-authoring -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install HoangNguyen0403/agent-skills-standard quality-engineering-test-plan-authoring --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standard.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/quality-engineering/quality-engineering-test-plan-authoring .claude/skills/quality-engineering-test-plan-authoring && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
quality-engineering-test-plan-authoring
GitHub stars
572
Token cost
~782 tokens
SKILL.md length
315 words
Files
8 (incl. references)
Skills in repo
211
Repo updated
First seen
Licence
MIT

At a glance

Turn acceptance criteria into an executable test plan (scenarios, seed, selector gaps) before generating E2E code.

  • ACs exist but no runnable test plan does yet
  • SKILL.md covers Priority: P1 (HIGH), Input, Output and Seed, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Tasks that involve Test generation

What it does

Quality Engineering Test Plan Authoring is an agent skill from HoangNguyen0403/agent-skills-standard. Turn acceptance criteria into an executable test plan (scenarios, seed, selector gaps) before generating E2E code. Use when ACs exist but no runnable test plan does yet.

Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including reference files (for example `evals/evals.json`, `references/ac-scenario-mapping.md` and `references/golden-requirements.md`).

It sits in Testing & QA, covering Test generation and End-to-end testing. The repository describes itself as: A collection of Agent Skills Standard and Best Practice for Programming Languages, Frameworks that help our AI Agent follow best practies on frameworks and programming laguages. The licence is MIT.

When your agent uses it

  • ACs exist but no runnable test plan does yet
  • Tasks that involve Test generation
  • Tasks that involve End-to-end testing

Example prompts

  • “/quality-engineering-test-plan-authoring”

What it can do on your machine

Read from SKILL.md and the folder at commit b529c2d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Quality Engineering Test Plan Authoring loads about 782 tokens when it runs, and up to ~3k if it reads all its reference files. Until then it costs about 52 tokens; SKILL.md has 315 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~52
When it runs · the whole SKILL.md, loaded when a task matches
~782
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from HoangNguyen0403/agent-skills-standard at commit b529c2d, republished under its MIT licence (© HoangNguyen0403). 315 words, ~782 tokens.

Download SKILL.mdSave it as .claude/skills/quality-engineering-test-plan-authoring/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
quality-engineering-test-plan-authoring
description
Turn acceptance criteria into an executable test plan (scenarios, seed, selector gaps) before generating E2E code. Use when ACs exist but no runnable test plan does yet.
guardrail
true

Quality Engineering: Test Plan Authoring

Priority: P1 (HIGH)

Input

AC-* IDs and SRS lanes (unit/integration/E2E-web/E2E-mobile/API) from the approved PRD/SRS. Never derive scenarios from reading the code — code shows what exists, not what the acceptance criteria require.

Output

docs/srs/test-plan-[slug].md (and specs/[slug].md once Playwright Test Agents are initialised on the target repo). Each scenario block: Steps, Expected, @AC-n tag, priority, exactly one lane (web|ios|android|api). One scenario covers one AC condition — do not fold multiple conditions into one scenario.

Seed

tests/seed.spec.ts (or platform equivalent) carries only shared prerequisites: auth and navigation to the starting screen. No assertions.

Mandatory Sections

Selector Gaps (elements the plan needs that have no stable id yet — feeds specialist-testid-inserter) and Data & Reset (fixtures needed, how state resets between scenarios). Gaps must follow the <screen>-<element>-<role> naming convention defined in quality-engineering-selector-stability.

Scenario Classes

Each AC condition expands to P (positive), N (negative: a stated condition violated), and E (edge: boundary of a stated condition). Classes must differ by precondition or input, never by phrasing. Every Expected cites its AC or business rule, or is tagged ASSUMED and surfaced under an Assumed Results header. On a HALT trigger (ultra-short AC, no expected behavior, bundled ACs, contradiction, undefined state) stop and ask; return HALT: <trigger> in autonomous mode.

Relationship to Zephyr

Manual Zephyr TCs stay the system of record for business sign-off (quality-engineering-zephyr-test-generation); this skill's scenarios carry a bidirectional TC-key reference where one exists, and are additive, not a replacement.

Anti-Patterns

  • A scenario without an Expected outcome.
  • A plan derived from source code instead of AC-*.
  • Duplicating unit-level coverage in an E2E scenario.
  • A scenario spanning more than one lane.
  • A plan with no seed reference.
  • A negative scenario that only rephrases the positive.
  • An expected outcome not traceable to an AC and not tagged ASSUMED.

References

© HoangNguyen0403, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 7 other files (references) in skills/quality-engineering/quality-engineering-test-plan-authoring of HoangNguyen0403/agent-skills-standard.

  • SKILL.md
  • evals/evals.json
  • references/ac-scenario-mapping.md
  • references/golden-requirements.md
  • references/mobile-lane-matrix.md
  • references/playwright-agents-artifacts.md
  • references/scenario-expansion.md
  • references/test-plan-template.md

Open the folder on GitHubat commit b529c2d

Compare with similar skills

Quality Engineering Test Plan Authoring next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Quality Engineering Test Plan Authoring compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Quality Engineering Test Plan Authoring this skillHoangNguyen0403/agent-skills-standard572—~782Automated safety check: PassMIT
Add E2E Test Suitecrowdin/crowdin-cli320—~2.4kAutomated safety check: PassMIT
E2E Test ThinkerUniClipboard/UniClipboard1.9k—~1.7kAutomated safety check: PassAGPL-3.0
Migrate E2E To Integrationopenshift/oc-mirror124—~1.5kAutomated safety check: PassApache-2.0
Verifying ChangesMr-Quin/danmaku-anywhere547—~1.1kAutomated safety check: PassCustom licence
Bmad Testarch Automatebmad-code-org/bmad-method-test-architecture-enterprise105—~1.5kAutomated safety check: PassCustom licence

Similar skills

  • Add E2E Test Suite

    crowdin/crowdin-cli

    Adds a new end-to-end (e2e) test suite for the Crowdin CLI under tests/e2e/suites/, exercising real CLI commands against a freshly-created Crowdin project.

    320 GitHub stars~2.4k tokensUpdated 2 days ago
    Testing & QAAuto-check passed
  • E2E Test Thinker

    UniClipboard/UniClipboard

    Analyze the current branch's diff against main and determine which changes are testable via CLI-based end-to-end tests.

    1.9k GitHub stars~1.7k tokensUpdated today
    Testing & QAAuto-check passed
  • Migrate E2E To Integration

    openshift/oc-mirror

    Migrate an oc-mirror e2e test case to the integration test suite, translating framework, registry, invocation, and assertion patterns

    124 GitHub stars~1.5k tokensUpdated 3 days ago
    Testing & QAAuto-check passed
  • Verifying Changes

    Mr-Quin/danmaku-anywhere

    Use after changing extension code, to prove it works: which test tier to run, the red-before-green rule, and what to record in the PR test plan.

    547 GitHub stars~1.1k tokensUpdated today
    Testing & QAAuto-check passed
  • Bmad Testarch Automate

    bmad-code-org/bmad-method-test-architecture-enterprise

    Generate tests in red or expand mode and run-and-heal new tests.

    105 GitHub stars~1.5k tokensUpdated today
    Testing & QAAuto-check passed
  • Test Scenarios

    phuryn/pm-skills

    Create comprehensive test scenarios from user stories with test objectives, starting conditions, user roles, step-by-step actions, and expected outcomes.

    27k GitHub stars~866 tokensUpdated 2 days ago
    Testing & QAAuto-check passed

More from HoangNguyen0403/agent-skills-standard

All 211 skills in this repo
  • Subagent-Driven Development

    HoangNguyen0403/agent-skills-standard

    Runs a multi-task implementation plan by sending each task to a fresh implementer subagent, reviewing it independently, then reviewing the whole branch.

    572 GitHub stars~1.3k tokensUpdated 2 days ago
    Auto-check passed
  • draw.io Architecture Diagramming

    HoangNguyen0403/agent-skills-standard

    Draws architecture diagrams as editable draw.io files from a JSON spec, with a fixed house style, one C4 level per diagram and evidence-tagged shapes.

    572 GitHub stars~1.3k tokensUpdated 2 days ago
    Auto-check passed
  • Android Navigation 3 Guide

    HoangNguyen0403/agent-skills-standard

    Implements and migrates to Jetpack Navigation 3 in Compose: NavDisplay, typed route objects, a state-list back stack, deep links, multiple back stacks and dialog scenes.

    572 GitHub stars~687 tokensUpdated 2 days ago
    Auto-check passed
  • Angular HttpClient Standards

    HoangNguyen0403/agent-skills-standard

    Sets rules for Angular HTTP code: functional interceptors, typed requests, services that own every call, and httpResource for reactive data loading in Angular 17+.

    572 GitHub stars~652 tokensUpdated 2 days ago
    Auto-check passed
  • Angular Tooling

    HoangNguyen0403/agent-skills-standard

    Angular CLI usage, code generation, build configuration, and bundle optimization.

    572 GitHub stars~743 tokensUpdated 2 days ago
    Auto-check passed
  • Common Code Review

    HoangNguyen0403/agent-skills-standard

    Conduct high-quality, persona-driven code reviews. An agent skill from HoangNguyen0403/agent-skills-standard.

    572 GitHub stars~772 tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Quality Engineering Test Plan Authoring

What does Quality Engineering Test Plan Authoring do?

Turn acceptance criteria into an executable test plan (scenarios, seed, selector gaps) before generating E2E code. Quality Engineering Test Plan Authoring is an agent skill from HoangNguyen0403/agent-skills-standard. Turn acceptance criteria into an executable test plan (scenarios, seed, selector gaps) before generating E2E code.

When should I use Quality Engineering Test Plan Authoring?

Quality Engineering Test Plan Authoring fits situations like: ACs exist but no runnable test plan does yet; tasks that involve Test generation; tasks that involve End-to-end testing.

How do I install Quality Engineering Test Plan Authoring in Claude Code?

Run `npx skills add HoangNguyen0403/agent-skills-standard --skill quality-engineering-test-plan-authoring -a claude-code`. Or copy the skill folder (skills/quality-engineering/quality-engineering-test-plan-authoring in HoangNguyen0403/agent-skills-standard) into .claude/skills/quality-engineering-test-plan-authoring in your project. Claude Code loads it when a task matches its description.

How do I install Quality Engineering Test Plan Authoring in Codex?

Run `npx skills add HoangNguyen0403/agent-skills-standard --skill quality-engineering-test-plan-authoring -a codex`. Or copy the skill folder (skills/quality-engineering/quality-engineering-test-plan-authoring in HoangNguyen0403/agent-skills-standard) into .agents/skills/quality-engineering-test-plan-authoring in your project. Codex loads it when a task matches its description.

Can I use Quality Engineering Test Plan Authoring in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add HoangNguyen0403/agent-skills-standard --skill quality-engineering-test-plan-authoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/quality-engineering-test-plan-authoring, .gemini/skills/quality-engineering-test-plan-authoring, .github/skills/quality-engineering-test-plan-authoring and .opencode/skills/quality-engineering-test-plan-authoring in your project.

What does Quality Engineering Test Plan Authoring need to run?

SKILL.md names no scripts, command-line tools or credentials: Quality Engineering Test Plan Authoring is instructions for the agent only.

Does Quality Engineering Test Plan Authoring access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Quality Engineering Test Plan Authoring safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Quality Engineering Test Plan Authoring use?

Quality Engineering Test Plan Authoring is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Quality Engineering Test Plan Authoring use?

About 782 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.2k tokens, read only when the agent opens those files.

What are the alternatives to Quality Engineering Test Plan Authoring?

Skills that share tags, products or a category with Quality Engineering Test Plan Authoring: Add E2E Test Suite (crowdin/crowdin-cli, 320 stars), E2E Test Thinker (UniClipboard/UniClipboard, 1.9k stars), Migrate E2E To Integration (openshift/oc-mirror, 124 stars) and Verifying Changes (Mr-Quin/danmaku-anywhere, 547 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Quality Engineering Test Plan Authoring?

HoangNguyen0403 (a GitHub user) maintains it in HoangNguyen0403/agent-skills-standard, which has 572 GitHub stars. The repository holds 211 skills in this directory. The repository was last updated on October 9, 2026.

Source: HoangNguyen0403/agent-skills-standard on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.