workflow-integration-test

Codex compatibility note:

• Invoke $skill-name: load the registered .agents/skills/<name>/SKILL.md and execute it with Codex tools; no separate Skill tool or Claude mode switch is needed. Author .claude/**; mirrors are generated.
• Track steps before execution and keep progress/evidence current. Explicit skill requests execute their protocol. Use the native question tool for required questions.
• Map foreign tool names to available host capabilities. A name mismatch needs no approval; an actually unavailable required capability stops with its step/evidence and a user question before adaptation.
• Subagent authorization: when a skill is user-invoked or AI-detected and its protocol requires subagents, that skill activation authorizes use of the required spawn_agent subagent(s) for that task.
• Preserve protocol order unless the user approves a deviation. Workflows use $start-workflow: gates stay fixed; other steps may flex with logged reasons and evidence.

Workflow Calls and Todo Bootstrap

Read the registry → workflows.workflow-integration-test together with this skill. Call $start-workflow workflow-integration-test to resolve the selected mode, pre-actions and fingerprint.

Todo FIRST: before triage, analysis or step execution, create one todo per phase of the selected mode, in order, listing every occurrence of that phase as a line, including conditional/optional ones (a mode that declares no phases gets one todo per occurrence); preserve occurrence IDs, roles and barrier groups. Use native todo tools or an equivalent persistent ledger. Then mark the first todo in_progress; close each step line with its run or skip evidence, and complete a phase todo only when every line is closed and its applicable exit gates hold. Mode selection and registry loading prepare tracking; any 'first action' below means the first substantive action after this bootstrap.

Call each step skill: read its linked SKILL.md and execute its protocol through the active host with the registry args. Reading or naming a skill alone is not execution. Required gates and core/optional flex follow the linked start-workflow Step Execution Protocol; keep this skill's quality gates, loops and evidence requirements.

Conditions: load each occurrence's registry applicability.when and skipReason verbatim, and record its run/skip evidence through the linked start-workflow protocol. Do not silently omit a todo or turn a conditional skill into an unconditional call; close, in one batch at triage, the todos whose condition is already false there. Declared parallel groups retain their all-return barrier.

Explicit step-skill calls by mode (registry order; roles and conditions remain owned by the registry):

• Mode write: $investigate (core) → $spec [mode=tests] (optional; conditional) → $work-item --mode=review --type=spec-tests (optional; conditional) → $integration-test (core) → $integration-test --mode=review (gate) → $integration-test --mode=verify (gate) → $spec [mode=sync] (gate) → $docs-manager --mode=update (optional; conditional) → $workflow-end (gate) → $watzup (optional; conditional) Phase todos: Discover (1) → Specify (2) → Build (1) → Review (1; exit review-converged) → Verify (3; exit tests-pass, spec-synced) → Close (2; exit run-closed)

• Mode green: $investigate (optional; conditional) → $integration-test --mode=verify --fix-loop (gate) → $spec [mode=sync] (optional; conditional) → $docs-manager --mode=update (optional; conditional) → $workflow-end (gate) → $watzup (optional; conditional) Phase todos: Discover (1) → Verify (3; exit tests-pass, root-cause-traced, spec-synced) → Close (2; exit run-closed)