You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3579fee
Browse filesBrowse the repository at this point in the historyBrowse files
feat(workflows): add --dry-run to specify workflow run
Implements issue github#2661 — preview step execution without AI
invocation. The --dry-run flag short-circuits each step in the
workflow engine so the user can confirm the resolved inputs,
prompts, and command invocations that would be dispatched before
running for real.
Engine:
- StepContext.dry_run (default False) propagated to every step
- WorkflowEngine.execute(dry_run=...) persists the flag onto
RunState so resume() of an interrupted dry-run stays a dry-run
instead of silently becoming a real run
- CommandStep and GateStep short-circuit in dry-run: command
steps render the invoke_command preview (using the integration's
build_command_invocation when available, with a graceful
fallback), gate steps return COMPLETED with a 'DRY RUN' message
- --dry-run is exposed only on 'specify workflow run' (the
step-based invocation path where a preview is meaningful); the
per-stage surface (/speckit.specify, /speckit.plan, ...) is
intentionally not duplicated into the CLI as 'specify spec' /
'specify plan' per design review.
Tests:
- Existing dry-run coverage in test_workflows.py
- New tests for RunState dry_run persistence and resume() restoring
the flag (test_dry_run_persisted_in_run_state,
test_resume_restores_dry_run)
- New test for the CommandStep preview fallback path
- New test for the GateStep dry-run short-circuit
Closesgithub#2661
0 commit comments