recipe-plan

SKILL.md

Context: Dedicated to the planning phase.

Orchestrator Definition

Core Identity: "I am not a worker. I am an orchestrator." (see subagents-orchestration-guide skill)

Execution Protocol:

  1. Delegate all work to sub-agents — your role is to invoke sub-agents, pass data between them, and report results
  2. Follow subagents-orchestration-guide skill planning flow exactly:
    • Execute steps defined below
    • Stop and obtain approval for plan content before completion
  3. Scope: Complete when work plan receives approval

CRITICAL: When the user requests test generation, always execute acceptance-test-generator first — it provides the test skeleton that work-planner depends on.

Scope Boundaries

Included in this skill:

  • Design document selection
  • Test skeleton generation with acceptance-test-generator
  • Work plan creation with work-planner
  • Plan approval obtainment

Responsibility Boundary: This skill completes with work plan approval.

Follow the planning process below:

Execution Process

Step 1: Design Document Selection

! ls -la docs/design/*.md | head -10

  • Check for existence of design documents, notify user if none exist
  • Present options if multiple exist (can be specified with $ARGUMENTS)

Step 2: E2E Test Skeleton Generation Confirmation

  • Confirm with user whether to generate E2E test skeleton first
  • If user wants generation: Generate test skeleton with acceptance-test-generator
  • Pass generation results to next process according to subagents-orchestration-guide skill coordination specification

Step 3: Work Plan Creation

  • Create work plan with work-planner
  • Utilize deliverables from previous process according to subagents-orchestration-guide skill coordination specification
  • Interact with user to complete plan and obtain approval for plan content
  • Clarify specific implementation steps and risks

Scope: Up to work plan creation and obtaining approval for plan content.

Response at Completion

Recommended: End with the following standard response after plan content approval

Planning phase completed.
- Work plan: docs/plans/[plan-name].md
- Status: Approved

Please provide separate instructions for implementation.
Weekly Installs
1
GitHub Stars
202
First Seen
3 days ago
Installed on
amp1
cline1
opencode1
cursor1
kimi-cli1
codex1