writing-plans

Write implementation plans with bite-sized tasks, exact file paths, and complete code.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/CHENHUI-X/toolbox --skill writing-plans-chenhui-x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/CHENHUI-X/toolbox/tree/main/custom-skills/software-development/writing-plans
Command: npx skills add https://github.com/CHENHUI-X/toolbox --skill writing-plans-chenhui-x

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Vague or incomplete implementation plans force developers to guess at file paths, code details, and verification steps, causing bugs and rework. This Skill produces structured implementation plans where every task is small, explicit, and copy-pasteable. ## Core Features & Use Cases - Bite-Sized Task Breakdown: Splits features into 2-5 minute tasks, each with one clear action such as writing a failing test or committing changes. - Complete Task Templates: Every task includes exact file paths, full code examples, exact commands with expected output, and verification steps. - TDD and Git Discipline: Enforces test-driven development cycles, DRY and YAGNI principles, and frequent commits throughout the plan. - Use Case: Before building a multi-step feature like user authentication, generate a plan that decomposes it into tasks such as creating the User model, adding password hashing, and writing tests, then hand it off for subagent-driven execution. ## Quick Start Ask the agent to write an implementation plan for your feature, breaking it into small TDD tasks with exact file paths and complete code.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I write an implementation plan for a new feature?

Start by understanding requirements and exploring the codebase, then design the approach and write sequential tasks. Each task should take 2-5 minutes and include exact file paths, complete code, test commands with expected output, and a commit step.

How to break down a complex feature into small tasks?

Decompose the feature so each task is one action, such as writing a failing test, running it, implementing minimal code, or committing. For example, split authentication into creating the User model, adding a password hash field, and building a hashing utility.

What should a good implementation plan include?

A good plan includes a header with goal, architecture, and tech stack, followed by tasks with objectives, exact file paths, complete copy-pasteable code, exact commands with expected output, and verification steps. It applies DRY, YAGNI, and TDD principles.

When should I write an implementation plan before coding?

Write a plan before implementing multi-step features, breaking down complex requirements, or delegating work to subagents. Even simple features benefit, since assumptions cause bugs and documentation helps future maintenance.

What are common mistakes in implementation plans?

Common mistakes include vague tasks like "add authentication", incomplete code snippets, missing verification steps, and unspecified file paths. Each task should name exact files, provide full code, and state the command and expected result.