make-plan

Create structured, phase-based implementation plans with documented source citations.

17|7|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/thedotmack/crab-mem --skill make-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: make-plan
Source: https://github.com/thedotmack/crab-mem/tree/main/skills/make-plan
Command: npx skills add https://github.com/thedotmack/crab-mem --skill make-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill creates phased implementation plans with documentation discovery to guide complex feature work.

Core Features & Use Cases

  • Plan phases: Break down large features into clear, executable phases with documentation references.
  • Documentation discovery: Automatically identify relevant docs, examples, and patterns to cite in plans.
  • Verification & governance: Enforce a subagent reporting contract and phase-by-phase verification to ensure traceability.

Quick Start

Write a new plan file under plans/ named after your feature, e.g., plans/new-feature.md, and begin with Phase 0 research and documented APIs.

Frequently Asked Questions about make-plan

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

FAQPage Schema
How do I create a phase-based implementation plan for complex software features?

You can break down complex software features into executable phases by writing a plan file under plans/ and starting with Phase 0 research. This workflow outputs publishable plan documents with staged phases and clear acceptance criteria.

What is documentation discovery in software planning?

Documentation discovery automatically identifies relevant docs, examples, and patterns to cite in implementation plans. This ensures plans are knowledge-driven and include explicit source citations for complex, multi-file projects.

How do I ensure verification and traceability across multi-file project phases?

You can ensure verification and traceability by enforcing a subagent reporting contract and phase-by-phase verification. This approach guarantees verifiable milestones and clear acceptance criteria throughout the workflow.

Does doc-driven planning work for large multi-file software projects?

Yes, doc-driven planning works for large multi-file software projects by requiring explicit documentation discovery and verifiable milestones. It guides complex feature work through staged phases with source citations and governance.

What are the limitations of using subagents for phase-by-phase verification?

Using subagents for phase-by-phase verification requires strict enforcement of a reporting contract. This mandates explicit documentation discovery and verifiable milestones, which may slow down rapid prototyping for simple tasks.