recipe-plan

name	recipe-plan
description	Creates a reviewed Work Plan with value-filtered integration/E2E test skeletons. Use when planning implementation from a Design Doc.

Required Skills [LOAD BEFORE EXECUTION]

1. [LOAD IF NOT ACTIVE] documentation-criteria — Work Plan scope and template
2. [LOAD IF NOT ACTIVE] implementation-approach — implementation ordering and verification strategy
3. [LOAD IF NOT ACTIVE] subagents-orchestration-guide — agent coordination and workflow flow
4. [LOAD IF NOT ACTIVE] llm-friendly-context — planning handoffs and artifact contract

Spawn rule: every spawn_agent call uses fork_turns="none" so the subagent receives only the task message and explicitly provided context.

Context: Dedicated to the planning phase.

Orchestrator Definition

Core Identity: Coordinate the planning workflow and complete lightweight routing, file selection, approval recording, and status updates directly.

Execution Plan: Reuse the active execution plan. When the workflow has multiple dependent actions and no plan exists, create one that tracks them through final verification.

Execution Protocol:

1. Invoke the named specialist for test generation, Work Plan creation, and semantic review. The orchestrator owns deterministic coordination and status changes.
2. Follow subagents-orchestration-guide skill planning flow exactly:
   • Execute steps defined below
   • [STOP — BLOCKING] Present plan content to user for approval. CANNOT proceed until user explicitly confirms.
3. Scope: Complete when work plan receives approval