home / skills / duc01226 / easyplatform / plan-two
This skill helps you generate two detailed implementation plans with trade-offs, validation prompts, and collaboration steps for a given task.
npx playbooks add skill duc01226/easyplatform --skill plan-twoReview the files below or copy the command above to add this skill to your agents.
---
name: plan-two
description: "[Planning] ⚡⚡⚡⚡ Research & create an implementation plan with 2 approaches"
argument-hint: [task]
infer: true
---
Think harder.
Activate `plan` skill.
> **CRITICAL:** Do NOT use `EnterPlanMode` tool — it blocks Write/Edit/Task tools needed for plan creation. Follow the workflow below.
> **Planning is collaborative:** Validate plan, ask user to confirm, surface decision questions with recommendations.
## Your mission
Use the `planner` subagent to create 2 detailed implementation plans for this following task:
<task>
$ARGUMENTS
</task>
## Workflow
1. First: Create a directory using naming pattern from `## Naming` section in injected context.
Make sure you pass the directory path to every subagent during the process.
2. Follow strictly to the "Plan Creation & Organization" rules of `plan` skill.
3. Use multiple `researcher` agents in parallel to research for this task, each agent research for a different aspect of the task and perform max 5 researches (max 5 tool calls).
4. Use `scout` agent to search the codebase for files needed to complete the task.
5. Main agent gathers all research and scout report filepaths, and pass them to `planner` subagent with the detailed instructions prompt to create an implementation plan of this task.
**Output:** Provide at least 2 implementation approaches with clear trade-offs, and explain the pros and cons of each approach, and provide a recommended approach.
6. Main agent receives the implementation plan from `planner` subagent, and ask user to review the plan
## Plan File Specification
- Every `plan.md` MUST start with YAML frontmatter:
```yaml
---
title: "{Brief title}"
description: "{One sentence for card preview}"
status: pending
priority: P2
effort: {sum of phases, e.g., 4h}
branch: {current git branch}
tags: [relevant, tags]
created: {YYYY-MM-DD}
---
```
## MANDATORY: Plan Collaboration Protocol (READ THIS)
- **Do NOT use `EnterPlanMode` tool** — it blocks Write/Edit/Task tools needed to create plan files and launch subagents
- **Do NOT start implementing** — plan only, wait for user approval
- **ALWAYS validate:** After plan creation, execute `/plan-review` to validate the plan
- **ALWAYS confirm:** Ask user to review and approve the plan using `AskUserQuestion` with a recommendation
- **ALWAYS surface decisions:** Use `AskUserQuestion` with recommended options for key architectural/design decisions
- **Planning = Collaboration:** The plan is shaped by user input — never treat it as a unilateral output
- Always plan and break many small todo tasks
- Always add a final review todo task to review the works done at the end
- Sacrifice grammar for concision. List unresolved questions at the end
This skill helps research and produce two distinct, detailed implementation plans for a given task and recommends one approach. It organizes work into a plan directory, runs parallel research and codebase scouting, and prepares plan.md files that follow a strict frontmatter spec. The skill emphasizes collaboration: it surfaces decision questions, requests user confirmation, and halts before any implementation.
It creates a named plan directory and launches multiple parallel researcher agents (max 5) to gather domain, dependency, testing, integration, and risk information. It uses a scout agent to locate relevant code files and then hands research and file paths to a planner subagent that generates at least two implementation approaches with trade-offs. The workflow mandates plan-only output, a final /plan-review validation step, and explicit AskUserQuestion prompts for decisions and approval.
Will this skill start implementing code after plan creation?
No. It stops at plan creation and requests your approval before any write/edit tasks. Implementation only begins after you explicitly approve and trigger it.
How many researcher agents will run and what do they cover?
Up to 5 researcher agents run in parallel, each covering a different aspect you or the skill designate (e.g., dependencies, integration points, performance, security, testing).
What does the produced plan file include?
Each plan.md begins with required YAML frontmatter (title, description, status, priority, effort, branch, tags, created) and breaks work into small TODOs, phases, and a final review task.
How are decisions surfaced to me?
Key design/architecture choices are presented as AskUserQuestion prompts with recommended options and a recommended approach; unresolved questions are listed at the end of the plan.