make-plan

Generate phased implementation plans with documentation references and verification checklists.

11|2|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/ajsai47/holyclaude --skill make-plan-ajsai47
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: make-plan
Source: https://github.com/ajsai47/holyclaude/tree/main/skills/memory/make-plan
Command: npx skills add https://github.com/ajsai47/holyclaude --skill make-plan-ajsai47

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the common issue of implementation plans that rely on unverified API assumptions, overlook existing codebase patterns, or skip critical verification steps, which leads to costly rework, failed builds, and wasted development time.

Core Features & Use Cases

  • Automated Documentation Discovery: Deploys subagents to gather and validate existing APIs, code patterns, and documentation before planning begins, ensuring all plan steps are grounded in actual codebase reality.
  • Structured Phased Planning: Generates LLM-friendly, self-contained implementation phases with explicit documentation references, copy-ready code snippet locations, verification checklists, and anti-pattern guards to prevent invalid implementation choices.
  • Use Case: Ideal for software teams planning new features or complex tasks, where you need to ensure the implementation plan aligns with existing code standards and documented APIs to avoid building non-functional or redundant code.

Quick Start

Use the make-plan skill to create a phased implementation plan for adding user profile editing functionality to the existing React application, including all required documentation references and verification steps.

Frequently Asked Questions about make-plan

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

FAQPage Schema
How do I create an implementation plan that doesn't rely on unverified API assumptions?

Phased development planning prevents failed builds by generating self-contained implementation phases with explicit documentation references and verification checklists. This structured approach ensures each task aligns with existing code standards before execution begins.

How does subagent orchestration work for gathering codebase documentation?

Yes, documentation-backed planning applies to development teams of all sizes for feature planning, multi-step implementation design, and pre-execution task breakdown. It scales by validating APIs and codebase patterns regardless of your project's scope.

What is the best way to structure a phased implementation plan for a complex feature?

Anti-pattern prevention works by embedding anti-pattern guards directly into your implementation phases. These guardrails actively prevent invalid implementation choices by verifying that each step aligns with documented APIs and existing codebase patterns before execution.

Why does my software implementation plan fail during execution despite passing initial reviews?

Verification checklists are required for implementation planning because they validate that each phase aligns with documented APIs and existing code patterns. Without these checklists, unverified assumptions lead to non-functional code and costly rework.