create-plan

Create phased implementation plans with milestones, risks, and success criteria.

4|1|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/carterbs/agent-config --skill create-plan-carterbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-plan
Source: https://github.com/carterbs/agent-config/tree/main/plugins/brad-personal/skills/create-plan
Command: npx skills add https://github.com/carterbs/agent-config --skill create-plan-carterbs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Create detailed implementation plans to guide multi-file features, architectural changes, and milestone-based projects with clear success criteria before coding.

Core Features & Use Cases

  • Planning framework that decomposes work into phases and milestones.
  • Research-driven approach to understand requirements and existing code.
  • Structured templates for documenting decisions, risks, and rollout strategies.

Quick Start

Provide the project goal, constraints, and any known risks, and I will generate a phased implementation plan with milestones and success criteria.

Frequently Asked Questions about create-plan

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

FAQPage Schema
How do I create a phased implementation plan for a multi-file software feature?

To create a phased implementation plan, provide your project goal, constraints, and known risks to generate a structured plan with milestones, phase-specific tasks, and clear success criteria.

What is the best way to document architectural decisions and risks before coding?

The best way to document architectural decisions and risks is using a structured planning template that records decision logs, risk mitigation strategies, and rollout strategies for major refactors.

How do I plan a major software refactor with clear milestones?

You plan a major software refactor with milestones by decomposing the architectural changes into phases, applying a research-driven approach to understand existing code, and defining success criteria.

Can I use this for research-backed project management of new feature launches?

Yes, you can use this research-backed project management approach for major feature launches, as it satisfies requirements for formal plan structure, milestone tracking, and documented decisions.

Do I need to provide existing codebase documentation to generate an implementation plan?

You do not need existing codebase documentation, but providing your project goal, constraints, and any known risks allows the research-driven planning framework to generate accurate phase-specific tasks.

When should I not use a structured planning framework for software development?

You should not use a structured planning framework for simple, single-file updates that do not require milestones, risk analysis, or multi-phase implementation efforts with documented decisions.