plan-before-code

Plans implementation approach, verification steps, and task breakdown before writing code.

96|8|Updated Aug 13, 2026
One-click install
npx skills add https://github.com/pingfanfan/hello-dsh --skill plan-before-code-pingfanfan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-before-code
Source: https://github.com/pingfanfan/hello-dsh/tree/main/examples/skills/plan-before-code
Command: npx skills add https://github.com/pingfanfan/hello-dsh --skill plan-before-code-pingfanfan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers often jump into multi-file or uncertain tasks without a clear plan, only to discover halfway through that the approach was wrong and hours of work must be redone. This Skill enforces a think-first workflow so requirements, existing code patterns, and verification methods are settled before any code is written. ## Core Features & Use Cases - Requirement Clarification: Prompts you to confirm the real problem, scope boundaries, and constraints before designing, and to ask only questions whose answers change the approach. - Written Plan with Verification: Requires a written plan covering what changes, why this approach, how to verify with concrete commands or steps, and known risks. - Verifiable Task Breakdown: Splits work into steps where each step ends in a committable, working state, and schedules the most uncertain part first. - Use Case: You are asked to add a data export feature touching the backend, API, and UI. Before coding, the Skill walks you through confirming the actual need, checking for existing export utilities, writing a plan with a concrete verification command, and sequencing the work so the system never sits in a broken intermediate state. ## Quick Start Use the plan-before-code skill to help me plan the implementation of a user notification system before I start writing any code.

Frequently Asked Questions about plan-before-code

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

FAQPage Schema
How do I plan a coding task before writing code?▼

Start by confirming the real problem, scope boundaries, and constraints. Then survey existing code for reusable patterns, write a short plan covering what changes, why this approach, and how to verify it with concrete commands, and split the work into steps that each end in a committable state.

When should I write an implementation plan versus coding directly?▼

Write a plan when the task touches multiple files, involves uncertainty, or would take more than half a day to redo if wrong. Skip the planning overhead for single-file changes that take ten minutes and can be reverted instantly.

How do I break a large coding task into smaller steps?▼

Split the work so every step ends in a verifiable, committable state where the system still works. For example: add data structures first, implement new logic with tests second, switch callers third, then delete the old implementation.

What are signs that my implementation plan is wrong?▼

Warning signs include scope expanding beyond the plan, needing to modify something you assumed was untouched, discovering a simpler approach mid-way, or being stuck on the same problem for over thirty minutes. Stop and rethink rather than pushing forward.

Should I do the hardest or most uncertain part of a task first?▼

Yes, tackle the most uncertain part first, such as an unfamiliar library or API. If it proves unworkable you must redesign the plan, and doing it last risks invalidating all earlier work. A small throwaway verification script can eliminate the uncertainty cheaply.