code-planning

Decompose software projects into actionable tasks with verification criteria.

2|1|Updated Jun 30, 2019

Search Tags:#planning #verification #trade-offs #risk-management #task-decomposition #scope-management #plan-structure

Ready to run

npx skills add https://github.com/tgautier/dotfiles --skill code-planning

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-planning
Source: https://github.com/tgautier/dotfiles/tree/main/claude/skills/code-planning
Command: npx skills add https://github.com/tgautier/dotfiles --skill code-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning discipline for structuring implementation plans. Helps teams evaluate trade-offs, decompose work, manage scope, and identify risks before coding.

Core Features & Use Cases

Trade-off evaluation: compare alternative approaches and select robust options.
Task decomposition: break features into atomic tasks with clear verification steps.
Scope management: define exclusions and guardrails to prevent scope creep.
Risk identification: surface integration and dependency risks early.
Plan structure & verification: provide templates and checklists for end-to-end plans.
Annotation cycle: support iterative refinement of plans before implementation.

Quick Start

Create a step-by-step task decomposition plan for a project, including a sample structure and verification criteria.

Frequently Asked Questions about code-planning

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

FAQPage Schema

How do I decompose a software project into actionable tasks with clear verification criteria?▼

Task decomposition breaks software features into atomic tasks with defined verification steps. This approach provides templates and checklists to structure implementation plans, ensuring traceable execution workflows and clear scope management before coding begins.

What is the best way to evaluate trade-offs and identify risks during project planning?▼

Trade-off evaluation in project planning compares alternative approaches to select robust options. It surfaces integration and dependency risks early, applying risk-management principles to prevent scope creep and ensure plan quality before development starts.

How do you manage scope creep when structuring implementation plans?▼

Scope management defines explicit exclusions and guardrails within implementation plans. By setting boundaries during the task decomposition phase, teams prevent scope creep and maintain focus on verified deliverables throughout the development effort.

Can I use task decomposition for iterative plan refinement before coding?▼

Task decomposition supports iterative plan refinement through an annotation cycle. This allows teams to iteratively evaluate plan structure, manage scope, and refine tasks before implementation, ensuring high plan quality and early risk identification.

Does project planning work for complex software development efforts with multiple dependencies?▼

Project planning scales for complex software development efforts by identifying integration and dependency risks early. It provides end-to-end plan structure with clear verification criteria, traceable execution workflows, and scope guardrails for robust execution.

What limitations exist when trying to structure implementation plans without dedicated risk assessment?▼

Structuring implementation plans without dedicated risk assessment limits the ability to surface integration and dependency risks early. It prevents proper trade-off evaluation and leaves scope management guardrails undefined, reducing overall plan quality before coding.