creating-planslisted

<PLANNER-ONLY> This skill runs ONLY inside the `planner` agent (always Opus), 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 Opus, 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 Opus).** It does not write code and does not invoke orchestrating-delivery. Its only output is a validated `execution-plan.json`. **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):** `references/validate-plan.mjs` **Valid example:** `references/example-plan.json` User-facing messages are always in pt-br. All identifiers, JSON keys, file paths, and reasoning stay in English. --- ## Step 1 — Read the spec Extract and list explicitly: - User journeys (`#uj-N`) — these drive `demo.scenarios_from_refs` - Acceptance criteria (`#ac-N.M`) — these drive `loc