name	workflow-gate
description	Evaluate and advance the thin workflow gate contract for task-state

workflow-gate

Use this skill when the task already has a task-state and the next move depends on ownership, handoff, review, QA, verification, or investigation evidence.

Flow

Read the current state with stack-pilot internal task-state show --json.
Check the next phase with stack-pilot internal gate check --target-phase plan|execute|review|qa|ship --json.
Add missing signals with stack-pilot internal task-state advance --complete ....
Keep the resumable lane current with stack-pilot internal task-state advance --summary "..." --checkpoint "..." when the stopping point changes.
Advance only after the gate report is clean with stack-pilot internal gate apply --target-phase ... --json.
When verification fails, record the failure with stack-pilot internal task-state advance --increment-attempt --failure "...".
After the second failed attempt, attach investigation evidence with stack-pilot internal task-state advance --investigation-note "...".

Contract

phase-gate requires spec before plan.
phase-gate requires plan before execute.
ralph-retry requires investigation evidence after repeated failed attempts.
parallel-build requires ownership before execution moves forward.
parallel-build requires handoff before review, QA, or ship.
review-gate requires review, qa, and verify before ship.
incident requires investigation evidence after repeated failed attempts.
Spec-driven lanes should name their validator before execution: command, test, schema, UI check, API contract, or manual acceptance proof.

Gstack-style Lane

Treat gstack as a workflow contract source, not as a runtime dependency.
Owner maps must be explicit before delegated or parallel execution.
Handoffs must capture objective, acceptance target, owner map, touched files, verification, risks, and next action.
Validators must stay reproducible enough for a later agent or human to rerun without reconstructing the whole conversation.
Prefer provider-native agents, skills, or commands for execution after the gate is clean.

Output

target phase
missing signals
validator
command run
remaining risk

workflow-gate

Use this skill when the task already has a task-state and the next move depends on ownership, handoff, review, QA, verification, or investigation evidence.

Flow

Read the current state with stack-pilot internal task-state show --json.

Check the next phase with stack-pilot internal gate check --target-phase plan|execute|review|qa|ship --json.

Add missing signals with stack-pilot internal task-state advance --complete ....

Keep the resumable lane current with stack-pilot internal task-state advance --summary "..." --checkpoint "..." when the stopping point changes.

Advance only after the gate report is clean with stack-pilot internal gate apply --target-phase ... --json.

When verification fails, record the failure with stack-pilot internal task-state advance --increment-attempt --failure "...".

After the second failed attempt, attach investigation evidence with stack-pilot internal task-state advance --investigation-note "...".

Contract

phase-gate requires spec before plan.

phase-gate requires plan before execute.

ralph-retry requires investigation evidence after repeated failed attempts.

parallel-build requires ownership before execution moves forward.

parallel-build requires handoff before review, QA, or ship.

review-gate requires review, qa, and verify before ship.

incident requires investigation evidence after repeated failed attempts.

Spec-driven lanes should name their validator before execution: command, test, schema, UI check, API contract, or manual acceptance proof.

Gstack-style Lane

Treat gstack as a workflow contract source, not as a runtime dependency.

Owner maps must be explicit before delegated or parallel execution.

Handoffs must capture objective, acceptance target, owner map, touched files, verification, risks, and next action.

Validators must stay reproducible enough for a later agent or human to rerun without reconstructing the whole conversation.

Prefer provider-native agents, skills, or commands for execution after the gate is clean.

Output

target phase

missing signals

validator

command run

remaining risk