What is give-plan used for?

To create actionable implementation plans and not write code.

What files does the plan generate?

A plan.md and phase-XX-*.md files inside a dated folder plans/YYYYMMDDHHmm-{plan-name}, following the templates and constraints.

When is implementation started?

Only after explicit user approval; give-plan guides planning, not execution.

give-plan

Scanned

npx machina-cli add skill Vibe-Builders/claude-prime/give-plan --openclaw

Files (1)

SKILL.md

1.4 KB

Ultrathink.

Role

You are a strategic planner. Create actionable implementation plans — not implementation.

Process

Check conversation context and skip completed steps.

1. Research (if needed)

Execute /research for codebase context and patterns
Skip if research already done in conversation

2. Plan

Create a progressive disclosure structure:

plans/YYYYMMDDHHmm-{plan-name}/
  plan.md           # Overview (<80 lines)
  phase-01-*.md     # First phase details
  phase-02-*.md     # Second phase details
  ...

Use date +%Y%m%d%H%M for timestamp.

3. Review

Present plan to user for approval. NO implementation until explicit approval.

plan.md Template

Keep under 80 lines:

Problem summary (what we're solving)
Solution approach (high-level how)
Phase list with status
Success criteria
Key risks and mitigations

phase-XX.md Template

Each phase file includes:

Overview and dependencies
Requirements and implementation steps
Success criteria
Risks

Constraints

NO implementation code in plans
Break large plans into independently deliverable phases
Be honest about complexity and risks

Request

<request>$ARGUMENTS</request>

Source

git clone https://github.com/Vibe-Builders/claude-prime/blob/main/.claude/skills/give-plan/SKILL.mdView on GitHub

Overview

give-plan creates detailed, multi-phase implementation plans before coding. It targets multi-file changes, architectural work, or complex features, delivering a structured plan folder (plans/YYYYMMDDHHmm-{plan-name}) with plan.md and phase-XX-*.md files. This reduces risk by aligning scope, dependencies, and success criteria prior to execution.

How This Skill Works

The tool checks the conversation context, optionally runs /research for codebase context, and then generates a plans/YYYYMMDDHHmm-{plan-name}/ folder. Inside, plan.md provides an overview (kept under 80 lines) and phase-01-*.md, phase-02-*.md, etc., for progressive disclosure. No code is generated; implementation starts only after explicit user approval.

When to Use It

Planning multi-file changes or architectural work before coding
Outlining a major redesign or refactor across modules
Planning a complex feature with dependencies and phased delivery
Assessing a tech stack or toolchain migration prior to commit
Preparing risk-aware, independently deliverable project phases

Quick Start

Step 1: Gather context and goals for the planned work (scope, constraints, success).
Step 2: Generate a plans/YYYYMMDDHHmm-{plan-name} structure with plan.md and phase-01-*.md.
Step 3: Present the plan for review and obtain explicit approval before any implementation.

Best Practices

Define scope and success criteria up front to guide the plan
Use plan.md to summarize the problem, high-level solution, and dependencies
Break work into independent, deliverable phases with clear milestones
List risks and mitigations for each phase to set expectations
Present the plan for explicit approval; no implementation until approved

Example Use Cases

Plan a database schema overhaul across multiple services with phased migrations
Plan a frontend component library migration and UI consistency changes
Plan a microservices boundary rewrite with interface and data contract updates
Plan a CI/CD pipeline upgrade across environments with rollback steps
Plan performance optimizations spanning caching, async processing, and queues

Frequently Asked Questions

Add this skill to your agents