threnody-planlisted

# Threnody planning mode Unified **planning entry point** for normal orchestration (`plan_task`) and swarms (`execute_swarm`). Detect plan-only vs plan-then-execute from user wording. ## Trigger phrases **Plan-only:** "plan only", "dry run", "show waves", "preview the swarm", "don't execute yet", "what agents would you spawn" **Plan-then-execute:** default when user asks to build/implement/refactor without plan-only qualifiers **Always plan first:** multi-file, multi-concern, or parallel agent work Host-native plans auto-fan out to **one agent per file** when intent implies a webapp/fullstack stack (`heuristic_intent_templates`). Use `expand_host_plan` after scaffold waves if more files appear. For broad code review, prefer the token-cheap `FAST_REVIEW:` shape (one read-only reviewer per file plus synthesis). Use the deeper `REVIEW:` file × dimension swarm only when the user explicitly asks for deep review, security-critical audit, threat modeling, or a named specialist dimension. ## Fast-start contract Any plan path that emits agents must return a spawnable `host_spawn_waves` handoff quickly: target **under 5 seconds** to handoff and **under 30 seconds** to first host spawn. Keep optional LLM refinement, consensus, detailed receipts, and learning aggregation off the first-spawn path. When executing a returned plan, spawn **all agents in the same wave as one batch** before waiting at the wave barrier. Never serialize agents inside a single wave. ## Workflow ### 1.