pr-plan

Topics in the source

• Step 1 — Combine and interview
• Step 2 — Codex review of the plan
• Step 3 — Emit the OpenSpec change (OpenSpec repos only)
• Step 4 — Make the plan durable, then 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 1 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. Treat the tracker issue body + comments AND whatever I typed when invoking /la:pr as the combined brief. In case of conflict, what I typed has higher priority but ask to be sure. Living-architecture repos: the la:living-architecture skill's "Working under the architecture" rules apply before drafting. The plan MUST state which element principles apply, and any arc42 contradiction is raised as its own interview point. If the change adds a capability, the plan also records where its spec attaches: one e

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