pr-tests

Topics in the source

• Step 1 — Write the tests first
• Step 2 — Codex review of the tests against the plan
• Step 3 — Commit the changed files
• Step 4 — Hard stop

Preflight: run la-doctor --plugin --require-config --require-plan-store once per session before using any la- or dr- command. If it reports the missing-config finding (the one naming /la:init), run the fast path of the la:init skill, then re-run this preflight; stop and show the user its output on anything it still reports, or on any other failure. Stage 2 of 4 of the /la:pr flow. Prerequisite: /la:pr has run in this session and established BRANCH, CHANGEID, OPENSPEC, and the full tracker issue (body + comments), if there is one. If any of that is missing, invoke the la:pr skill instead — it rehydrates and dispatches back here. The /la:pr stopping policy applies throughout this stage. Before writing anything, recover the durable plan from pr-plan: OPENSPEC=1 — read the whole change folder openspec/changes/ / (proposal, design, tasks, delta specs). OPENSPEC=0 — the finalized plan is a comment on the tracker issue. TDD-first: land the full test suite for the agreed plan before writing any implementation. Tests should fail for the right reason (feature missing), not for setup reasons. If OPENSPEC=1, derive the test cases from the delta scenarios in openspec/changes/ /specs/ /spec.md:

This is an excerpt. Refer to the complete source and its current requirements.