skills.rest
pckienuit
pckienuitCOMMUNITY
Explore all skills by this author →
GitHub

plan-writing

Break complex software work into ordered plans with dependencies and verification criteria.

Updated Mar 30, 2026
Search Tags:#planning#refactoring#implementation#bug fixing#verification#task breakdown
One-click install
npx skills add https://github.com/pckienuit/GameDev1 --skill plan-writing-pckienuit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-writing
Source: https://github.com/pckienuit/GameDev1/tree/main/.cursor/skills/plan-writing
Command: npx skills add https://github.com/pckienuit/GameDev1 --skill plan-writing-pckienuit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps turn ambiguous or multi-step work into a concise, actionable plan with clear ordering, dependencies, and verification criteria.

Core Features & Use Cases

  • Task Breakdown: Split implementation, refactoring, or bug-fix work into small, independently verifiable steps.
  • Verification Guidance: Define exactly how each step will be checked so progress is easy to confirm.
  • Project-Specific Planning: Adapt the plan to the type of work, whether it is a new feature, a fix, or a broader codebase change.
  • Use Case: A developer preparing to add authentication can use this Skill to outline the files to change, the order of work, and the tests needed to prove the feature is complete.

Quick Start

Ask for a concise implementation plan for your current coding task, including ordered steps and a verification check for each step.

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 complex software implementation task into actionable steps?▼

To break down a complex software implementation task, split the work into concise, ordered action items with clear dependencies and verification criteria. This ensures reliable execution by defining exactly how each step will be checked before moving forward.

What is the best way to plan a codebase refactoring project with verifiable progress?▼

Planning a codebase refactoring project requires dividing the work into small, independently verifiable steps. Define task ordering, dependencies, and specific verification guidance to confirm progress easily at each stage of the refactoring process.

Can I create a bug fixing plan that includes specific verification criteria?▼

Yes, you can create a bug fixing plan that includes specific verification criteria. The plan breaks the fix into small steps and defines exactly how each step will be checked, ensuring progress is easy to confirm and the bug is reliably resolved.

Does task planning work for new feature implementation and bug fixes?▼

Task planning works for new feature implementation, bug fixes, and refactoring. It adapts the plan to the specific type of work, outlining files to change, the order of work, and the tests needed to prove the feature is complete and reliable.

Why do I need task sizing and dependencies for software development planning?▼

Task sizing and dependencies are required for software development planning to ensure reliable execution. Sizing breaks work into manageable steps, while dependencies establish clear ordering so each step is independently verifiable and correctly sequenced.

Related Skills

Explore More Software Engineering Skills→
coff33ninjacoff33ninja

requirements-clarify

Guide structured Q&A to define project scope and objectives.

Community
Intermediate
m-xlseam-xlsea
319

verification

Run tests, measure coverage, and validate acceptance criteria in CI pipelines.

Community
Intermediate
ribon-orgribon-org

plan

Generate structured implementation plans with steps and verification criteria.

Official
Basic
achmfachmf

plan-writing

Create structured, verifiable task plans for software development projects.

Community
Intermediate