plan-writing

Break down complex work into actionable tasks with verification criteria.

Updated Mar 27, 2026

Search Tags:#planning #dependencies #verification #milestones #project-management #task-breakdown

Ready to run

npx skills add https://github.com/theGobindSingh/cleantank --skill plan-writing-thegobindsingh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-writing
Source: https://github.com/theGobindSingh/cleantank/tree/main/.agents/skills/plan-writing
Command: npx skills add https://github.com/theGobindSingh/cleantank --skill plan-writing-thegobindsingh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning complex work can be chaotic without a clear breakdown. This skill provides a structured framework to decompose work into small, independently verifiable tasks with defined dependencies and verification criteria, reducing ambiguity and miscommunication.

Core Features & Use Cases

Small, focused tasks that take 2-5 minutes to complete and yield a single outcome.
Clear verification: each task includes a concrete way to confirm it is done.
Logical ordering and dependency awareness, with a recommended plan structure that avoids templated plans.
Dynamic naming: plan files are saved at the PROJECT ROOT with task-derived names; no inappropriate locations.
Best for: feature additions, refactors, or any multi-step work requiring careful coordination.

Quick Start

Draft a concise plan at the project root with 5–10 tasks, each having a verifiable outcome.

Frequently Asked Questions about plan-writing

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

FAQPage Schema

How do I break down complex project work into verifiable tasks?▼

To break down complex work into verifiable tasks, you decompose multi-step projects into 2-5 minute focused outcomes with clear dependencies and concrete verification criteria, reducing ambiguity and miscommunication.

What is the best way to plan a multi-step feature implementation with dependencies?▼

The best way to plan a multi-step feature implementation is to sequence tasks with dependency awareness, creating a compact plan file at the project root that avoids templated structures and enforces project-specific planning principles.

Can I use this task breakdown approach for refactoring projects?▼

Yes, you can use this task breakdown approach for refactoring projects. It applies to feature implementation, refactors, or any multi-step work requiring careful coordination by guiding task scope and logical ordering.

How do I verify that a planned task is actually complete?▼

To verify a planned task is complete, each task in the breakdown includes a concrete way to confirm it is done. This ensures small, focused tasks yield a single, independently verifiable outcome.

Do I need any external dependencies to generate project plans?▼

No, you do not need any external dependencies to generate project plans. The skill operates independently to produce a compact, verifiable plan file dynamically named and saved at the project root.

Why avoid templated plans for multi-step project work?▼

You should avoid templated plans for multi-step project work because they lack project-specific planning principles. This approach ensures logical ordering and dependency awareness with a recommended plan structure tailored to your actual work.