plan

Restate requirements, identify risks, and generate a phased implementation plan.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/Eotel/claude-marketplace --skill plan-eotel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/Eotel/claude-marketplace/tree/main/plugins/base/skills/plan
Command: npx skills add https://github.com/Eotel/claude-marketplace --skill plan-eotel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restates ambiguous requirements, surfaces risks early, and provides a clear, step-by-step plan before any code is written.

Core Features & Use Cases

  • Requirements restatement: Clarifies goals so the team is aligned.
  • Risk assessment: Identifies blockers and dependencies to address proactively.
  • Phased plan: Generates a concrete, multi-phase implementation plan with milestones.
  • Guardrails: Enforces explicit user confirmation before proceeding with any changes.

Quick Start

Provide a project brief and request a plan to generate a structured, phased approach.

Frequently Asked Questions about plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a phased implementation plan for complex multi-file projects?▼

To create a phased implementation plan, you provide a project brief to restate requirements, assess risks, and generate a step-by-step plan with milestones before coding begins.

What is the best way to identify risks and blockers before feature development?▼

Risk assessment is performed by restating project goals and proactively surfacing dependencies and blockers, ensuring the team addresses potential issues before writing any code.

How do I enforce explicit user confirmation before proceeding with architectural changes?▼

You enforce explicit user confirmation by applying guardrails that require approval at each planning milestone, ensuring accountability before any implementation changes proceed.

When do I need upfront planning for software engineering tasks?▼

Upfront planning is needed for feature development, architectural changes, and complex multi-file projects where clarifying ambiguous requirements early reduces implementation risk.

Can I use this planning approach to clarify ambiguous project requirements?▼

Yes, you can use this approach to clarify ambiguous requirements by restating the project brief, aligning team goals, and producing a concrete plan before development starts.