pr-implement

原文涵盖的主题

• Step 1 — Implement until tests pass
• Step 2 — Local gates (before commit)
• Step 3 — Ask me to push and open the PR
• 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 3 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 (the openspec/changes/ / folder when OPENSPEC=1, else the plan comment on the tracker issue) and the failing tests already on disk from pr-tests. Implement the plan. Run the repo's test command (la-config get commands.test; if unset, the repo's documented full non-integration suite) after changes and fix any failures. Do not declare done until every test from the pr-tests stage passes. An existing test that breaks because it pins what the plan changes

这里只展示节选，请以完整原文和当前要求为准。