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.
- 0
- Installs
- —
- Rating
- —
- Success rate
- 8
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 0cbf8dcf1ba11b64… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
SKILL.md
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
Expectedoutcome. - 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
Files
8- SKILL.md
3db21cddac3.1 KB - evals/evals.json
2a2723e2164.3 KB - references/ac-scenario-mapping.md
de0503671e469 B - references/golden-requirements.md
cc03dd00b73.2 KB - references/mobile-lane-matrix.md
4c672b8411552 B - references/playwright-agents-artifacts.md
8db4e6415f872 B - references/scenario-expansion.md
ddb17379133.2 KB - references/test-plan-template.md
61c147ff12511 B
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from HoangNguyen0403/agent-skills-standard8
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.
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 spec
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.
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.
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.
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 reci
Configure release signing, R8 obfuscation, and App Bundle publishing for Android. Use when setting up signing configs, enabling minification, adding ProGuard keep rules, or preparing for Play Store submission.
Enforce Material Design 3 theming and design token usage in Jetpack Compose. Use when implementing M3 components, color schemes, typography, or design tokens.