ready

Verify readiness for AI-driven development: $ARGUMENTS

Core references. A citation of the form workflows-core:<name> names a shared reference in the workflows-core plugin. Load it with Skill(skill: "workflows-core:reference", args: "<name>") — never by path: ${CLAUDE_PLUGIN_ROOT} resolves to this plugin, which does not carry it.

/ready is the artifact-anchored readiness gate. Given a PRD or Epic address, it derives the workflow phase from the artifacts present and checks whether the ARD/spec/design artifacts that actually exist, taken together, justify that phase and the next transition, against the rubric in ${CLAUDE_PLUGIN_ROOT}/references/workflow-states.md — and, with --claimed "<status>", additionally compares the phase the operator declares against the derived one. It returns SUPPORTED / PARTIAL / NOT-SUPPORTED with a requirement coverage roll-up and named gaps, gated on the Opus readiness-reviewer.

Key distinction from every other pipeline command: /ready authors nothing in the PRD/Epic/ARD/spec/design sense — it never writes any of those, and it never writes a status. Its only authored write is an overwritten _readiness.md snapshot under $SPECS_PATH, and it branches only via the workflows-core:phase-handoff §4.3 consent choice to hand that snapshot off, creating ready/<KEY>-<slug> — specs-preflight itself still creates none, switching $SPECS_PATH only between branches that already exist and are plugin-created (workflows-core:specs-repo-git §2.2). _readiness.md is likewise committed only through that same §4.3 choice, never automatically — declining leaves it uncommitted; the terminal commit-artifacts step commits ONLY the run's bounded session-artifact paths (workflows-core:specs-repo-git §2.1), which _readiness.md is not. Where /design's repo gate is a strict, hard-stop mount check because it is about to ground code decisions, /ready's repo check is best-effort presence only — it never scans code, it only notes whether a needed repo is mounted.

Key distinction from every other consumer of workflows-core:phase-handoff §3 (require-on-main) and workflows-core:ard-resolution: every other caller's own gate stops it when a gated ARD/spec/design resolves off the specs repo's default branch (/product-workflows:brd-reconcile reads a stopping row without stopping at two sites and never at its ordinary Phase 0 gate — its cross-BRD write guard, and a --sent run's redundancy check at Phase 0 step 6, which reads the gate inverted; phase-handoff §3.7 names both); /ready never stops. That state becomes a readiness finding — "authored but not handed off" — that caps the eventual verdict at PARTIAL; an artifact that is absent outright is recorded as missing in the coverage roll-up, exactly as before this feature. Reporting readiness is /ready's whole function, so a run that stops instead of reporting has failed at the one thing it exists to do.

Key distinction from /design's Epic-picker behavior: a PRD- address is a first-class PRD-level check (workflow-states.md's PRD ladder), not something that must be resolved down to a single Epic. Address an EPIC- folder to scope the check to one Epic (the Epic ladder) instead.

Phase 0 — Resolve input

1. Resolve the address. Parse the single positional address from $ARGUMENTS — a <KEY>, or an @<path> naming a folder or a file inside one — and resolve it with resolve-address (Skill(skill: "workflows-core:reference", args: "addressing resolve-address"), §3). status: found → carry its path, kind and key forward; ambiguous → stop, naming every match. absent is a stop, not a folder to create — this command creates no folder in the specs tree. Surface the key dir not found rule in Skill(skill: "workflows-core:reference", args: "escalation-rules") (choices: ["Re-enter key", "Cancel"]) and name what does create one: a PRD- folder comes from /product-workflows:idea <KEY> or /product-workflows:create-prd <KEY> on the idea route and from /product-workflows:brd-split on its parent BRD on the BRD route; an EPIC- folder comes from /product-workflows:epics <PRD-ADDRESS> and from no other command.