planning

Generate ordered implementation plans from feature briefs via codebase analysis.

Updated Mar 17, 2017

Search Tags:#design #planning #codebase #implementation #task

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a feature brief or clear idea into a concrete, step‑by‑step implementation plan grounded in the actual codebase, eliminating vague speculation and the need for manual planning.

Core Features & Use Cases

Research: Analyzes the relevant parts of the repository and any external libraries to inform design decisions.
Design: Chooses where new code lives, outlines architectural choices, and flags risky areas.
Planning: Produces an ordered list of specific, self‑contained tasks ready for an implementation agent.

Quick Start

Ask the planning skill to create a step‑by‑step plan for the feature “Add dark mode support”.

Frequently Asked Questions about planning

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

FAQPage Schema

How do I generate an implementation plan from a feature brief?▼

Convert the brief into an actionable plan by analyzing the repository and external libraries to inform design decisions, choose where new code lives, and outline ordered implementation tasks.

What's the best way to plan software changes without writing code prematurely?▼

Producing an ordered list of specific, self-contained tasks from a feature description eliminates vague speculation and manual planning by grounding the design decisions in the actual repository.

Can I create a step-by-step development plan for an existing codebase?▼

Applying codebase analysis to a feature brief outlines necessary changes, flags risky areas, and produces an ordered list of specific, self-contained tasks ready for implementation.

Do I need a complete feature description to outline codebase changes?▼

A clear feature description is required to generate a concrete, step-by-step implementation plan, as it uses the feature brief to drive codebase research and architectural design decisions.

What is codebase analysis for software design planning?▼

Codebase analysis for design planning involves examining the repository to outline necessary changes, make architectural choices, and produce an ordered list of specific tasks without writing actual code.

When should I not use automated implementation planning?▼

Avoid automated implementation planning when lacking a clear feature brief or accessible codebase, as the process requires examining the repository to outline necessary changes and generate ordered tasks.