x4-test

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"}

X4 Test Orchestrator

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.

Trigger

User invokes /x4:test <change_name>

Purpose

Coordinate test-related workflow for a change by sequencing:

1. x4-test-doc (test docs)
2. x4-test-doc-viewer (final test-doc review gate)
3. x4-test-impl (test implementation)
4. x4-test-run (test execution + result apply)
5. x4-bug (bug registration when new product defects are found)
6. x4-bug-fix (product bug fix loop and re-verify)

Parameters

• <change_name>: target change under openspec/changes/.

Change Name Resolution (MANDATORY)

• Resolve to a single existing openspec/changes/<change-name> target before any action.
• If multiple/no matches, stop and ask user to choose.
• After resolution, print: Resolved change: <change-name>.

Mandatory Requirements

Chapter A: Agent-Only Mandatory

A.1 Orchestration Boundary (MANDATORY)

1. x4-test only orchestrates and routes work.
2. Do not duplicate detailed standards from phase skills.
3. Do not bypass required phase when user intent explicitly requires it.

A.2 Delegation Map (MANDATORY)

1. Test documentation changes -> delegate to x4-test-doc.
2. Test documentation final review gate -> delegate to x4-test-doc-viewer via dedicated isolated reviewer subagent.
3. Test authoring/fixing -> delegate to x4-test-impl.
4. Test run and result apply -> delegate to x4-test-run.
5. New product bug registration -> delegate to x4-bug.
6. Product bug fixing workflow -> delegate to x4-bug-fix.

A.3 Sequencing (MANDATORY)

Default sequence:

1. Ensure docs are current (x4-test-doc) when requirements changed.
2. Run reviewer gate (x4-test-doc-viewer) for final doc draft in a dedicated isolated reviewer subagent.
3. If reviewer rejects (review_status=rewrite_required), route back to x4-test-doc and repeat doc-review loop until pass.
4. Ensure implementation coverage (x4-test-impl) when tests missing/stale.
5. Execute and apply run results (x4-test-run).
6. Failure branch handling:
   • test_defect -> route back to x4-test-impl, then rerun x4-test-run.
   • product_bug:
     • if no existing bug record -> run x4-bug first,
     • then run x4-bug-fix,
     • then rerun x4-test-run for bug-targeted verification.
7. Repeat branch loop until no unresolved blockers or user stops.

A.4 Execution Agent Mode (MANDATORY)

When the runtime supports delegated execution capabilities:

1. If Agent Team / team-member execution is supported, x4-test MUST start and use team members for delegated phases.
2. If Agent Team is not supported but subagent execution is supported, x4-test MUST start and use subagents for delegated phases.
3. x4-test-doc-viewer remains a dedicated isolated reviewer execution and MUST stay isolated under either mode.
4. If neither Agent Team nor subagent capability is available, stop and report BLOCKED with the missing capability.

Chapter B: Update Mandatory

B.1 Progress Reporting (MANDATORY)

• Report delegated phase status in order:
  • x4-test-doc
  • x4-test-doc-viewer
  • x4-test-impl
  • x4-test-run
  • x4-bug (when triggered)
  • x4-bug-fix (when triggered)
• Surface blockers with exact phase ownership.

B.2 Handoff Integrity (MANDATORY)

• Pass consistent change target to all delegated phases.
• For x4-test-doc-viewer, pass minimal review-only handoff payload and keep it isolated from main thread context.
• Preserve run-result context when handing off into x4-test-run.
• Preserve failure classification context (test_defect / product_bug) for branch routing.
• Ensure product bug branch always maps to a bug id before entering x4-bug-fix.
• Do not alter per-phase output contracts.

Output

• Delegation plan and executed phase order
• Per-phase summary (x4-test-doc, x4-test-doc-viewer, x4-test-impl, x4-test-run, x4-bug, x4-bug-fix)
• Final blockers and next step

Example Usage

/x4:test storage-auto-fill