rcode-check-implementation-readinesslisted

<!-- Bridge status: not currently invoked by any rcode/workflows/*.md file (no delegate_to_skill cross-reference exists in either direction). Reachable only via direct phrase-trigger match or explicit @-inclusion. See AUDIT-redundant-work.md finding 3. --> @.rcode/references/karpathy-guidelines.md ## Overview Verify that PRD, UX designs, architecture decisions, and epics/stories are all aligned and ready for implementation. ## Workflow Follow the instructions in ./workflow.md. ## When NOT to use this skill Do NOT use during active implementation — if work is already in progress, use `rcode-correct-course` instead. Do NOT invoke for a single-artifact review (e.g. "check this PRD"); scope this skill to cross-artifact alignment checks before a phase starts. ## Output Format - Produces an alignment report with checklist format - Each artifact checked: PRD exists? | UX exists? | ADR exists? | Stories exist? | Cross-references match? - Final verdict: READY / BLOCKED (with explicit blockers) - Do NOT declare ready if any artifact is missing or references are stale ## Examples ### Happy Path **Input:** "Check if phase-03 is ready for implementation" **Expected behavior:** Read all artifacts in .rcode/phases/phase-03/. Cross-check references. Produce table with READY/MISSING per artifact. Final verdict with any blockers. ### Edge Case: Stale Cross-References **Input:** (PRD mentions a feature that has no corresponding story) **Expected behavior:** Report as BLOCKED: "PRD s