plan-writing

Name: plan-writing
Availability: InStock
Author: DevayoshaUS

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

41|Updated Apr 14, 2026

Search Tags:#planning #refactoring #verification #task breakdown #feature implementation #project plan

Ready to run

npx skills add https://github.com/DevayoshaUS/Women-scholarship --skill plan-writing-devayoshaus

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-writing
Source: https://github.com/DevayoshaUS/Women-scholarship/tree/main/hackathon-main%20%281%29/hackathon-main/.agent/skills/plan-writing
Command: npx skills add https://github.com/DevayoshaUS/Women-scholarship --skill plan-writing-devayoshaus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-step work like feature implementation, refactoring, and bug fixes often fails due to vague or overly long plans. This Skill produces short, specific, verifiable task breakdowns so every step has a clear outcome and a way to confirm it is done. ## Core Features & Use Cases - Task Breakdown Principles: Enforces small, focused tasks (2-5 minutes each) with one clear, independently verifiable outcome per task. - Flexible Plan Structure: Provides a minimal Goal/Tasks/Done-When format instead of rigid templates, adapting to new projects, feature additions, and bug fixes. - Verification-First Planning: Requires concrete verification steps (e.g., run a command, check an output) and places final verification last. - Use Case: When adding authentication to a web app, generate a plan like "Install next-auth, create /api/auth/[...nextauth].ts, verify by logging in with a test account" instead of a generic "add auth" item. ## Quick Start Ask the AI to write a plan for your task, for example: create a plan for adding user authentication to my Next.js app.

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 task breakdown for a coding project?▼

Break work into tasks of 2-5 minutes each with one clear outcome per task. Every task needs a concrete verification step, such as running a command or checking an output, and the full plan should stay under one page.

How many tasks should an implementation plan contain?▼

Keep plans to 5-10 clear tasks maximum. If a plan grows beyond that or exceeds one page, split it into multiple plans rather than adding sub-tasks and micro-steps.

Where should plan files be saved in a project?▼

Plan files are saved in the project root using a slug derived from the task name, such as auth-feature.md for an authentication task. They should never be placed inside .claude/, docs/, or temporary folders.

Should I use a fixed template for every project plan?▼

No. Plans should be unique to each task and project type. A new project plan covers tech stack and MVP scope, a feature plan covers affected files and dependencies, and a bug fix plan covers root cause and the test that confirms the fix.

When should I not use a structured task plan?▼

Skip formal planning for trivial single-step changes that need no verification criteria. The planning approach is intended for multi-step work like new projects, feature additions, complex bug fixes, and multi-file refactoring.