Menu
Orchestrate test workflow across x4-test-doc, x4-test-doc-viewer, x4-test-impl, x4-test-run, x4-bug, and x4-bug-fix. Trigger with /x4:test <change-name>.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when x4-e2e-test-doc-details needs fixture patch rules or helper guidance for X4 E2E test data.
Use when refining X4 `e2e_tests.md` into detailed E2E task, fixture, and implementation knowledge documents before Playwright implementation.
Use when creating or updating only the high-level X4 E2E test plan `e2e_tests.md` before detail expansion.
Review X4 E2E test documentation draft and gate x4-e2e-test-doc completion. Must run in a dedicated isolated subagent. Trigger with /x4:e2e-test-doc-viewer <change-name>.
Implement Playwright E2E tests for X4 changes from `e2e_test_tasks.md` and validate task-to-test mapping. Trigger with /x4:e2e-test-impl <change-name>.
Run change-scoped X4 Playwright E2E tests and validate implementation coverage against `e2e_test_tasks.md`. Trigger with /x4:e2e-test-run <change-name>.
| name | x4-test |
| description | Orchestrate test workflow across x4-test-doc, x4-test-doc-viewer, x4-test-impl, x4-test-run, x4-bug, and x4-bug-fix. Trigger with /x4:test <change-name>. |
| metadata | {"version":"1.0"} |
This skill is orchestration-only and coordinates test phases. It does not own detailed rules for doc format, test implementation mapping, or run-apply logic.
User invokes /x4:test <change_name>
Coordinate test-related workflow for a change by sequencing:
x4-test-doc (test docs)x4-test-doc-viewer (final test-doc review gate)x4-test-impl (test implementation)x4-test-run (test execution + result apply)x4-bug (bug registration when new product defects are found)x4-bug-fix (product bug fix loop and re-verify)<change_name>: target change under openspec/changes/.openspec/changes/<change-name> target before any action.Resolved change: <change-name>.x4-test only orchestrates and routes work.x4-test-doc.x4-test-doc-viewer via dedicated isolated reviewer subagent.x4-test-impl.x4-test-run.x4-bug.x4-bug-fix.Default sequence:
x4-test-doc) when requirements changed.x4-test-doc-viewer) for final doc draft in a dedicated isolated reviewer subagent.review_status=rewrite_required), route back to x4-test-doc and repeat doc-review loop until pass.x4-test-impl) when tests missing/stale.x4-test-run).test_defect -> route back to x4-test-impl, then rerun x4-test-run.product_bug:
x4-bug first,x4-bug-fix,x4-test-run for bug-targeted verification.When the runtime supports delegated execution capabilities:
x4-test MUST start and use team members for delegated phases.x4-test MUST start and use subagents for delegated phases.x4-test-doc-viewer remains a dedicated isolated reviewer execution and MUST stay isolated under either mode.BLOCKED with the missing capability.x4-test-docx4-test-doc-viewerx4-test-implx4-test-runx4-bug (when triggered)x4-bug-fix (when triggered)x4-test-doc-viewer, pass minimal review-only handoff payload and keep it isolated from main thread context.x4-test-run.test_defect / product_bug) for branch routing.x4-bug-fix.x4-test-doc, x4-test-doc-viewer, x4-test-impl, x4-test-run, x4-bug, x4-bug-fix)/x4:test storage-auto-fill