plan

Generate a structured plan.md with Goal, Approach, Detailed Changes, Considerations, and Todo sections.

Updated Aug 14, 2024
One-click install
npx skills add https://github.com/kokatsu/dotfiles --skill plan-kokatsu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/kokatsu/dotfiles/tree/main/.config/claude/skills/plan
Command: npx skills add https://github.com/kokatsu/dotfiles --skill plan-kokatsu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan Skill helps teams convert research and current code insights into a concrete, executable plan document, eliminating ambiguity in feature development.

Core Features & Use Cases

  • Structured plan.md generation with sections: Goal, Approach, Detailed Changes, Considerations, Todo List.
  • Non-code planning: ensures no code is produced during planning.
  • Read from research.md and source files to ground plans in reality, enabling efficient handoff to developers.

Quick Start

Generate a plan.md for a requested feature using the current research and codebase as context.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I generate a structured implementation plan for a software feature?

To generate a structured implementation plan, draft a document containing Goal, Approach, Detailed Changes, Considerations, and Todo sections grounded in research notes and codebase context.

What is a code-free implementation plan and when do I need one?

A code-free implementation plan outlines required software changes without writing actual code. It is needed to eliminate ambiguity and establish a concrete approach before development begins.

How do I convert research notes into an executable software development plan?

Convert research notes into an executable plan by reading existing research documents and source files, then synthesizing them into a structured plan document with defined goals and actionable todos.

Can I use research notes to plan software changes across an entire repository?

Yes, you can use research notes to plan software changes across a repository by reading current source files and research context to produce a comprehensive, structured feature plan document.

Does the implementation planning process produce code changes?

No, the implementation planning process ensures no code changes are produced. It strictly generates a detailed plan document to enable efficient handoff to developers for actual coding.