plan-writing

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

2|Updated May 30, 2026
One-click install
npx skills add https://github.com/virahitvin8/crafty-gis --skill plan-writing-virahitvin8
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-writing
Source: https://github.com/virahitvin8/crafty-gis/tree/main/GIT_STAR/.agent/skills/plan-writing
Command: npx skills add https://github.com/virahitvin8/crafty-gis --skill plan-writing-virahitvin8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Breaking down features, refactors, or bug fixes into clear, actionable tasks is error-prone and often produces vague or bloated plans. This Skill provides a framework for writing short, specific, verifiable task plans that keep implementation work on track. ## Core Features & Use Cases - Task Breakdown Principles: Enforces small, focused tasks (2-5 minutes each) with one clear, independently verifiable outcome per task. - Verification-First Planning: Every task includes a concrete "how to check" criterion, and a verification phase is always placed last. - Project-Specific Guidance: Adapts plan content to the project type (new project, feature addition, bug fix) instead of using fixed templates. - Use Case: When asked to add authentication to a web app, produce a concise plan file like auth-feature.md in the project root listing specific tasks such as installing next-auth and creating the API route, each with a verifiable check. ## Quick Start Ask the AI to create a structured implementation plan for your next feature or bug fix 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 break down a feature into actionable tasks?

Split the feature into tasks that each take 2-5 minutes with one clear outcome. Attach a concrete verification step to every task, such as running a command or checking a specific output, and order tasks by dependency.

How to write a good implementation plan for coding tasks?

Start with a one-sentence goal, list at most 10 specific tasks with verification criteria, and end with clear done conditions. Avoid generic steps like "set up project" in favor of exact commands and file paths.

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 template-based task planning?

Fixed templates produce bloated, generic plans that ignore project context. This approach uses principles instead of templates, adapting task content and verification scripts to the specific project type, whether frontend, backend, mobile, or database work.

When should I use structured task planning?

Use it when starting a new project, adding a feature, fixing a complex bug, or refactoring multiple files. It is most valuable for any multi-step work where tasks have dependencies and need clear completion criteria.