plan

Name: plan
Availability: InStock
Author: donygeorge

Generate milestone-driven implementation plans with testable exit criteria.

2|Updated Feb 16, 2026

Search Tags:#architecture #documentation #implementation #milestones #plan #exit-criteria

Ready to run

npx skills add https://github.com/donygeorge/claude-toolkit --skill plan-donygeorge

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/donygeorge/claude-toolkit/tree/main/skills/plan
Command: npx skills add https://github.com/donygeorge/claude-toolkit --skill plan-donygeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Feature planning and specification often lag, leading to vague requirements and drift during implementation. This Skill automates the creation of structured, milestone-driven plans that define clear exit criteria, testing requirements, and architectural decisions before coding begins.

Core Features & Use Cases

Milestone-based plans with explicit exit criteria that are testable.
Documentation generation to docs/plans/<feature-name>.md compatible with the /implement skill.
Customizable defaults and integration with toolkit.toml for team-specific workflows.

Quick Start

Run /plan <feature-name> to generate a detailed implementation plan.

Frequently Asked Questions about plan

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

FAQPage Schema

How do I generate an implementation plan with testable milestones for a new feature?▼

You create an implementation plan by defining milestones with explicit exit criteria, testing requirements, and architecture decisions. The plan is output to docs/plans/<feature-name>.md, providing structured guidance before coding begins.

What is the best way to document architecture decisions and exit criteria before development?▼

The best way to document architecture decisions and exit criteria is through milestone-driven plans. This approach defines testable requirements and structural choices in a markdown file to prevent vague requirements and implementation drift.

How does the generated feature plan integrate with the implement workflow?▼

The generated feature plan integrates with the implement workflow by outputting to docs/plans/<feature-name>.md. This file structure ensures downstream development can follow the defined milestones and exit criteria without needing time estimates.

Can I customize milestone planning defaults for team-specific software workflows?▼

Yes, you can customize milestone planning defaults using toolkit.toml. This configuration allows teams to tailor the generation of implementation plans and exit criteria to match specific software development workflows.

Why does my feature implementation plan not include time estimates?▼

Your feature implementation plan excludes time estimates to focus purely on milestone-driven clarity. By emphasizing testable exit criteria and architecture decisions, the plan guides subsequent development without the pressure of inaccurate timelines.