test-readinesslisted

Orchestrates the full test-readiness pipeline (phases 1–5), once per qualifying repo under repos/, each in its own worktree + branch. Runs test-inventory → test-design → test-migration → test-roadmap → test-fix in sequence per repo, starting from the first stale artifact. Invoked by the `shipwright-test-readiness` cron on a daily schedule; exits early for a repo when all of its phase artifacts are fresh.
app-vitals/shipwright · ★ 8 · Code & Development · score 71

Install: claude install-skill app-vitals/shipwright

# test-readiness skill ## Purpose Drive the complete test-readiness pipeline from the first stale phase to publication. This skill is the cron-facing entry point — it picks up where the staleness guard left off and runs all necessary phases to bring the docs current. ## When invoked By the `shipwright-test-readiness` cron, which runs `/shipwright:test-readiness --full --publish` daily. The cron fires unconditionally on schedule; the flags below decide what actually happens. ## Arguments Flags are additive — invoking with no flags preserves the original behavior (staleness-gated, phase 5 in dry-run), so agents still on the old cron prompt keep working unchanged. | Flag | Effect | |------|--------| | `--full` | Skip the staleness check entirely and run all phases 1→5 regardless of artifact freshness. Without it, the staleness gate decides the starting phase and exits early when everything is fresh. | | `--publish` | Run phase 5 as a **real publish** — forward real-queue mode to `/shipwright:test-fix` so it writes task-store tasks unattended (no confirmation gate — test-fix never has one, matching entropy-fix/error-fix). Without it, phase 5 runs `--dry-run` (preview only, no task-store writes). | | `--dry-run` | Explicit preview: phase 5 runs `--dry-run`. This is the default when `--publish` is absent. | ## Staleness check **Skipped entirely when `--full` is passed** (the cron's default) — all phases 1→5 run. The check below only applies when `--full` is absent. Before