code-planning

Translate research findings into executable task plans with dependencies and verification checkpoints.

Updated May 9, 2020
One-click install
npx skills add https://github.com/Fenntasy/dotfiles --skill code-planning-fenntasy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-planning
Source: https://github.com/Fenntasy/dotfiles/tree/main/claude/skills/code-planning
Command: npx skills add https://github.com/Fenntasy/dotfiles --skill code-planning-fenntasy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning disciplined approaches to translate research into actionable, decomposed plans with clear scope and risk controls.

Core Features & Use Cases

  • Planning Philosophy: defines a quality framework (correctness, coherence, robustness, maintainability) to guide every plan.
  • Trade-off Evaluation: structures comparisons between approaches using explicit constraints and decision matrices.
  • Task Decomposition: breaks work into atomic tasks with clear ownership, dependencies, and verification steps.
  • Scope Management: enforces explicit exclusions and guards against scope creep.
  • Risk Identification: identifies breaking changes, integration risks, data migration concerns, and rollback considerations.
  • Plan Structure: standardizes how plans are documented, including context, approach, tasks, risks, verification, and future work.
  • Anti-patterns: highlights common planning pitfalls and fixes.
  • Annotation Cycle: outlines iterative plan refinement with feedback before implementation.

Quick Start

Start by outlining the problem, identify constraints, and decompose the work into atomic tasks with verification steps.

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 executable tasks with dependency ordering?

Task decomposition breaks work into atomic tasks with clear ownership, dependencies, and verification checkpoints. You standardize plan documentation by outlining context, approach, tasks, risks, verification, and future work to ensure correctness and coherence.

What is the best way to evaluate trade-offs and manage scope creep during product planning?

Trade-off evaluation structures comparisons between approaches using explicit constraints and decision matrices. Scope management enforces explicit exclusions and guards against scope creep by defining a quality framework spanning correctness, coherence, robustness, and maintainability.

How do I identify integration risks and breaking changes when planning a software migration?

Risk identification highlights breaking changes, integration risks, data migration concerns, and rollback considerations during planning. Applying an annotation cycle enables iterative plan refinement with feedback before implementation to mitigate these risks.

What are common planning anti-patterns and how can I structure my implementation strategy to avoid them?

Common planning anti-patterns are avoided by standardizing plan structure and enforcing explicit task manifests with dependency ordering. Highlighting these pitfalls ensures your implementation strategy satisfies plan quality criteria for robustness and maintainability.

Can I use structured task decomposition for product initiatives that require complex decision matrices?

Structured task decomposition applies to software projects and product initiatives requiring trade-off evaluation. It translates research findings into concrete, executable tasks by defining explicit constraints and verification checkpoints.

Why does my implementation plan lack robustness and maintainability when translating research findings?

Plans lack robustness and maintainability without a defined quality framework and explicit task manifests. Applying structured plan documentation with verification checkpoints and dependency ordering corrects these common planning anti-patterns.