Skip to content
cccskills
FreePublished on GitHub

quality-engineering-test-plan-authoring

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.

The English summary is being prepared. Showing the original description.

Works withPlaywright

Run score Not tested

See how to install

Files included (8)

  • SKILL.md3.1 KB
  • evals/evals.json4.3 KB
  • references/ac-scenario-mapping.md469 B
  • references/golden-requirements.md3.2 KB
  • references/mobile-lane-matrix.md552 B
  • references/playwright-agents-artifacts.md872 B
  • references/scenario-expansion.md3.2 KB
  • references/test-plan-template.md511 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their specific skills.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test recipes to their specific skills.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

See all skills by HoangNguyen0403

Report a problem with this skill