oc-creating-planslisted

<PLANNER-ONLY> This skill runs ONLY inside the `planner` agent (always the planner model from routing), dispatched by orchestrating-delivery in Phase 1. If you are the main loop or the orchestrator and reached here directly, STOP: do not generate the plan yourself. **Dispatch the `planner` agent** and hand it the approved spec. Generating the plan in the main loop defeats the context isolation and the model routing the harness depends on (a cheap orchestrator must delegate architecture-grade reasoning to planner-tier model, not do it inline). The only exception is the `planner` agent itself running this skill. </PLANNER-ONLY> # Creating-Plans — Generating execution-plan.json from an approved spec **This skill runs inside the planner agent (always the planner model from routing).** It does not write implementation code or invoke orchestrating-delivery. Its artifact is exactly one validated JSON file at `.opencode/plans/<feature_id>/execution-plan.json`; the planner writes and revises that file directly. **Announce at the start (in pt-br):** "Usando creating-plans para gerar o execution-plan.json a partir da spec aprovada." **Pre-requisite:** approved spec/PRD with user journeys (UJs), acceptance criteria (ACs), and constraints. **Contract source of truth (executable):** shared `validate-plan` (OC native tool `validate-plan`, or `core/shared/lib/validate-plan.mjs`). **Valid example:** `references/example-plan.json` (if present) or schema self-check below. User-facing mess