jcdavis131 Readiness Report
The handoff is the most-read part of a long session. Structure beats prose; the operator acts item-by-item without re-deriving state.
The shape
Needs your input to go to production
1. <Item> — <pre-existing|introduced> — <issue ID>.
2. ...
Ready for review: <seed command>, <serve command>, open <feature> on :<port>.
Required elements
- Numbered list — only items genuinely the operator's call (credentials, brand, spec sign-off, prod provisioning).
- Classify pre-existing vs introduced this session.
- Tag with repo issue IDs (SEC-003, BLK-PROD) — grep-able, not prose.
- Deliberate non-actions — what was skipped and why (
document-non-action). - Exact kick-the-tires commands — seed, serve, port; no "how do I see it?" step.
What belongs in the list
Credentials, pricing/brand decisions, prod infra (Operator lane), spec sign-off, pre-existing security deferred without sign-off, evidence/claims that are product calls.
What does NOT belong
Recap of what was built (recap-on-long-session), internal TODOs yours to finish, vague "review the code".
Extended patterns
Open items with forward offers, release-gated prioritization, designed states, curated review tour, tool-gap alternatives: reference.md
Pair with
recap-on-long-session·document-non-action·validate-gate·respect-the-guard