plan-writing

Plan Writing - Structured Task Planning Skill

Skill Overview

Plan Writing is a structured task planning skill designed for developers. It helps you break complex work down into clear, actionable small tasks, each with well-defined validation criteria.

Use Cases

1. Starting a New Project from Scratch

When you need to start a new project from a blank slate, Plan Writing helps you determine the tech stack, define the MVP scope, plan the file structure, and map out a clear development path.

2. Feature Development and Additions

When adding new features to an existing project, the skill helps identify affected files, list required dependencies, plan implementation steps, and define how to validate the feature.

3. Code Refactoring and Bug Fixes

When handling complex bug fixes or multi-file refactoring, Plan Writing helps you identify the root cause, plan the scope of changes, and determine a testing strategy to ensure changes remain safe and controllable.

Core Features

Focused Small Task Decomposition

Break large work into independent tasks that can be completed in 2–5 minutes each. Each task focuses on a single, clearly defined outcome, ensuring progress is traceable and easy to complete.

Clear Validation Criteria

Define explicit “done” standards for every task—how to check, how to test, and what the expected output is—so results are measurable and verifiable.

Smart Dependency Ordering

Automatically identify dependencies between tasks, mark paths that can be worked on in parallel, highlight the critical path, and help you schedule work in a rational order to improve efficiency.

FAQs

What type of developers is Plan Writing suitable for?

It is suitable for all developers who need structured planning, whether independent developers, technical teams, or project management roles. It’s especially useful for scenarios involving frequent multi-step tasks, such as feature development, code refactoring, and system migrations.

Where should plan files be saved?

Plan Writing follows a dynamic naming principle: plan files are saved directly in the project root directory, named as {task-slug}.md (e.g., “Add authentication feature” → auth-feature.md). This ensures plan files are easy to access and remain closely tied to the project code.

How do I know if a task has been split small enough?

An effective task should meet three conditions: can be completed in 2–5 minutes, has a single clear outcome, and is independently verifiable. If a task requires multiple steps to complete or if the validation criteria are vague, it needs to be split further.