Menu
Create a new X4 change step-by-step. Use with /x4:new as orchestration; document details are owned by x4-doc.
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-new |
| description | Create a new X4 change step-by-step. Use with /x4:new as orchestration; document details are owned by x4-doc. |
This skill owns /x4:new orchestration.
It can rely on openspec-new-change, while X4 phase rules are defined here.
Create a new change iteratively with confirmation points.
change-name (optional; supports abbreviation token such as std)x4-user-workflow "Change Name Resolution" ruleschange-name using x4-user-workflow rules before any action.Resolved change: <change-name>.change-name and source context from the resolver.request.md source.request.md quality using x4-doc "request.md Positioning" standards before downstream generation.
If not satisfied, revise request.md first.openspec-new-change for base creation process.x4-doc for all document detail rules.