con un clic
x4-user-workflow
Describe command-to-skill relationships for X4 workflow.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Menú
Describe command-to-skill relationships for X4 workflow.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
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-user-workflow |
| description | Describe command-to-skill relationships for X4 workflow. |
This skill only defines command relationships and routing boundaries. It does not arrange concrete execution work inside phase skills.
/x4:discuss/x4:new/x4:ff/x4:doc/x4:test-doc/x4:test-doc-viewer/x4:apply/x4:bug/x4:bug-fix/x4:test-impl/x4:test/x4:test-run/x4:verify/x4:archiveDeprecated and out of active workflow scope:
/x4:pipe/x4:subdisx4-user-workflow owns:
/x4:discuss -> x4-discuss/x4:new -> x4-new/x4:ff -> x4-ff/x4:doc -> x4-doc/x4:test-doc -> x4-test-doc/x4:test-doc-viewer -> x4-test-doc-viewer/x4:apply -> x4-apply/x4:bug -> x4-bug/x4:bug-fix -> x4-bug-fix/x4:test-impl -> x4-test-impl/x4:test -> x4-test/x4:test-run -> x4-test-run/x4:verify -> x4-verify/x4:archive -> x4-archiveFor commands that accept change-name, phase skills should use the shared resolver policy:
openspec/changes/<change-name>Conflict handling:
/x4:ff may auto-create openspec/changes/<change-name>/openspec/changes/archive/x4-user-workflow must not define:
Those rules must stay in each delegated phase skill.