git:20260815.b98e2ab to git:20260915.3b2dc52

---

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

## Scope Boundaries

**Included in this skill**:

- Design document selection

- Test skeleton generation with acceptance-test-generator

- Work plan creation with work-planner

- Work plan review with document-reviewer

Follow the planning process below:

## Execution Process

### Step 1: Design Document Selection

Check for existence of design documents in docs/design/, notify user if none exist.

Present options if multiple exist (can be specified with $ARGUMENTS).

### Step 2: Integration/E2E Test Skeleton Selection

- Spawn acceptance-test-generator agent: "Generate the value-selected integration/E2E test skeletons from Design Doc at [design-doc-path]."

- Verify generated artifact paths and pass them to Step 3; an empty selection is valid

### Step 3: Work Plan Creation

- Spawn work-planner agent: "Create an implementation-focused work plan from design document at [design-doc-path]. Include generated test skeleton artifact paths from the previous step when present. Plan only repository implementation outcomes required by the Design Doc."

- Verify the returned Work Plan path and use it as the Step 4 review target

### Step 4: Work Plan Review

Spawn document-reviewer agent: "Review the work plan. doc_type: WorkPlan. target: [work-planner completed path]. Verify Design Doc implementation coverage, absence of added operational scope, dependency order, executable verification, optional Verification Focus, and Review Scope."

Branch on `verdict.decision`:

- `needs_revision` -> apply Review Resolution with work-planner, then review the updated plan

- `rejected` -> apply Orchestrator Escalation Resolution using the cited governing sources

- Summarize the implementation task set and any material choice the user is approving

## Completion Criteria

- [ ] Design document identified and selected

- [ ] Integration/E2E test skeleton selection completed and its artifact paths passed to work-planner

- [ ] Work plan created via work-planner

- [ ] Work plan reviewed via document-reviewer

## Response at Completion

```

Planning phase completed.

- Work plan: docs/plans/[plan-name].md

```