odoo-planning

Odoo Planning - the execution plan between design and code

Planning step only. Output: <SHARE_DIR>/plans/<slug>-<date>.md (resolve <SHARE_DIR>/<ISOLATE_DIR> via the resolve-capture-substitute protocol in ${CLAUDE_PLUGIN_ROOT}/snippets/state-root-resolution.md before the first Read/Write/Edit of a state-root path in this skill) - never production source. You do NOT compute the plan and do NOT write code: launch odoo-planner, then own the plan gate and the hand-off.

gap/brl  ->  odoo-solution-design (TDD + index.yaml)  ->  HUMAN approves SRS and design (text)
   ->  odoo-planning -> odoo-planner (the plan: build nodes + the lifecycle tail)
   ->  EnterPlanMode -> the ONE plan gate -> ExitPlanMode
   ->  intake Phase P serializes run-<id>.json  ->  the main agent runs the plan

Role

Turn an approved technical design into ONE lifecycle plan (the build nodes and the lifecycle tail, documentation included) by launching ONE leaf planner, odoo-planner. The plan is run by the main agent per ${CLAUDE_PLUGIN_ROOT}/skills/odoo-intake/references/plan-mode-schema.md § Running the plan. The documentation of the change is the tail nodes docs-module then docs-site (plan-mode-schema.md § Default tail), run after code/review/QA when their when: holds, ungated. The documentation target (module, site, both, none) comes from odoo-intake in the brief.

Input port - read the upstream artifacts BY POINTER (before dispatch)

Locate the upstream artifacts and pass their paths to the planner (never paste or re-derive them):

• Design DAG (OPTIONAL - none when no design was authored) - <SHARE_DIR>/designs/<master-slug>/index.yaml (dag_layers + dependency direction) for a master-child design, or the single-mode <SHARE_DIR>/designs/<slug>-<date>.md. When one exists the planner CONSUMES it and never recomputes it. When none exists the plan is derived from the development work and the field is an explicit none.
• Gap matrix - <SHARE_DIR>/gap-analysis/<slug>-<date>/gap-matrix.jsonl (or a BRL RTM under <SHARE_DIR>/brl/<job-id>/): per-requirement effort tier, drives effort.
• QA oracle (OPTIONAL - usually ABSENT at planning time) - <ISOLATE_DIR>/qa/<slug>-scenarios.md. The acceptance node is ALWAYS authored statically, never omitted for lack of an oracle. When the oracle is absent, the plan sources the node's criteria from the design's §9 Acceptance Criteria; when present, the plan wires its review/acceptance stages to it.
• Survey (OPTIONAL - ALWAYS an explicit value) - <SHARE_DIR>/survey/<slug>-<date>/synthesis.md, forwarded in this skill's brief INPUTS when intake's hand-off carried a deep-survey synthesis. State none explicitly to odoo-planner when absent, and thread it onward the same way (§ P1).