Skip to content
Back to skills

Creating A Plan

ASecurity

Creates a comprehensive easy to follow plan for building out a design. Use when creating an implementation plan from a design.

  • 666 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added February 8, 2026
documentation

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill creating-a-plan --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Creating A Plan?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Creating A Plan
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-creating-a-plan/badge)](https://www.skillsdirectory.com/skills/majiayu000-creating-a-plan)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: creating-a-plan
description: Creates a comprehensive easy to follow plan for building out a design. Use when creating an implementation plan from a design.
---

## Overview

Write a comprehensive implementation plan

- Assume the implementor has zero context for the codebase
- Assume the implementor is a skilled developer
- Document everything they would need to know
  - files that will be touched
  - useful reference code, unit tests, and docs
  - how to test changes
- Save all markdown docs next to the provided design
- Construct the plan as bite-sized tasks

## Plan structure

- Write the plan to `plan.md` next to the design
- Fill out the [plan template](./PLAN.md)

## Task Granularity

**Each step is one action (2-5 minutes):**
- "Write the failing test" - step
- "Run it to make sure it fails" - step
- "Implement the minimal code to make the test pass" - step
- "Run the tests and make sure they pass" - step
- "Commit" - step

## Task Batches

- Group tasks into coherent batches
- Write each batch to its own file, `batch-<number>.md`, next to the plan and design
- Use the [batch template](./BATCH.md)
- Always use exact file paths
- Always use code snippets and not ambiguous instructions like "add validation"
- Always use exact commands with expected output
- Batches should be incremental and build on each other. Batch 1 must be implemented before batch 2

**REMEMBER**:
- DRY
- YAGNI
- TDD
- frequent commits

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.