skills.rest
beliciobcardoso
beliciobcardosoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

plan-writing

Generates structured task plans with dependencies and verification criteria for multi-step work.

Updated Mar 17, 2026
Search Tags:#planning#project management#markdown#refactoring#verification#task breakdown#implementation plan
One-click install
npx skills add https://github.com/beliciobcardoso/mcp-postgres --skill plan-writing-beliciobcardoso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-writing
Source: https://github.com/beliciobcardoso/mcp-postgres/tree/main/.agent/skills/plan-writing
Command: npx skills add https://github.com/beliciobcardoso/mcp-postgres --skill plan-writing-beliciobcardoso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Breaking down features, refactors, or bug fixes into clear actionable steps is error-prone and often produces vague, unverifiable plans. This Skill provides a framework for writing short, specific, verifiable task plans. ## Core Features & Use Cases - Task Breakdown Principles: Enforces small, focused tasks of 2-5 minutes each with one clear, independently verifiable outcome. - Verification-First Planning: Every task includes a concrete "done" check, such as running a command or observing a specific output. - Flexible Structure: Rejects fixed templates in favor of dynamic content based on project type, whether new project, feature addition, or bug fix. - Use Case: When asked to add authentication to a web app, produce a plan file like auth-feature.md in the project root with 5-10 specific tasks, each with its own verification step. ## Quick Start Ask the AI to write an implementation plan for your next feature or refactor using the plan-writing skill.

Frequently Asked Questions about plan-writing

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

FAQPage Schema
How do I write a good implementation plan for a coding task?▼

Start with a one-sentence goal, then list 5-10 specific tasks, each with a concrete verification step such as running a command or checking an output. Keep the plan under one page and save it as a markdown file in the project root.

How to break down a feature into actionable development tasks?▼

Make each task small enough to complete in 2-5 minutes with one clear outcome. Identify dependencies between tasks, highlight the critical path, and always place a final verification phase last.

Should task plans use a fixed template?▼

No. This Skill explicitly rejects fixed templates in favor of dynamic content based on project type. A new project plan covers tech stack and MVP scope, while a bug fix plan focuses on root cause, the exact change, and how to test it.

Where should plan files be saved in a project?▼

Plan files are saved as markdown files named after the task slug, such as auth-feature.md, directly in the project root. They should never be placed inside .claude/, docs/, or temporary folders.

What are the limitations of task planning frameworks?▼

Plans longer than one page or with more than about 10 tasks become hard to follow and should be split into multiple plans. Overly generic tasks like "set up project" lack verifiable outcomes and defeat the purpose of structured planning.

Related Skills

Explore More Software Engineering Skills→
dealroom-aidealroom-ai

linear-issue-writing

Draft structured Linear issues with Problem, Solution, and Acceptance Criteria sections.

Official
Advanced
INNERJOINTINNERJOINT

ralph

Automate PRD-driven execution loops until all user stories pass verification.

Community
Advanced
shinprshinpr
675

recipe-review

Reviews completed implementations against design documents and applies user-approved corrections.

Community
Advanced
unblockedunblocked
13

headless-plan

Gather organizational context and produce a validated implementation plan without writing code.

Official
Advanced