test-readiness

To detect stale artifacts and refresh the pipeline, the system checks phase artifacts in your active worktree and starts execution at the first stale step rather than rerunning the entire workflow unnecessarily.

Orchestrate test inventory, design, migration, roadmap, and publish phases by running them sequentially; the pipeline stops immediately on failure to protect downstream outputs from inconsistent states.

Yes, you can run test-readiness workflows on a daily cron schedule. It supports unattended runs that can either preview updates or publish them directly for scheduled maintenance.

The best way to recover outdated documents is through manual recovery workflows that detect staleness and advance the pipeline from the correct starting phase to restore readiness.

Yes, the test-readiness pipeline supports dry-run publishing. You can preview updates without applying them, giving you control over whether changes are published or simply reviewed during unattended runs.

Sequential phase orchestration stops before the publish phase because a prior step failed; this failure stopping mechanism protects downstream outputs from being published with inconsistent data.