skills.rest
enigmaicon-eng
enigmaicon-engCOMMUNITY
Explore all skills by this author →
GitHub

make-plan

Create phased implementation plans from documentation discovery with verification checklists.

1|Updated May 16, 2026
Search Tags:#orchestration#implementation guidance#documentation discovery#API verification#phased planning#anti-pattern prevention
One-click install
npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill make-plan-enigmaicon-eng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: make-plan
Source: https://github.com/enigmaicon-eng/AI-Enterprise-OS/tree/main/examples/claude-mem/plugin/skills/make-plan
Command: npx skills add https://github.com/enigmaicon-eng/AI-Enterprise-OS --skill make-plan-enigmaicon-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you avoid guesswork by producing a detailed, phased implementation plan grounded in real documentation rather than assumptions.

Core Features & Use Cases

  • Documentation-first planning (Phase 0): Searches for and reads relevant docs/examples to identify actual APIs, methods, and signatures before designing the plan.
  • Orchestrator-led phased execution: Structures an LLM-friendly plan with clear phase boundaries and copy-from-docs instructions.
  • Verification and anti-pattern guards: Includes a checklist to confirm each phase worked and explicitly prevents invented APIs or undocumented parameters.
  • Use Case: When you need to add a new feature or implement a multi-step change, you can generate a plan that tells agents exactly what to copy and how to verify it.

Quick Start

Use the make-plan skill when you are asked to plan a feature, task, or multi-step implementation before executing with do.

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 phased implementation plan that prevents LLMs from inventing API signatures?▼

To create a phased implementation plan that prevents invented API signatures, enforce a Phase 0 documentation discovery step. This skill requires an allowed-APIs list with sources and includes anti-pattern guards against undocumented parameters before execution.

What is documentation-first feature planning for multi-step tasks?▼

Documentation-first feature planning searches and reads relevant docs to identify actual APIs before designing execution plans. It structures multi-step task orchestration with phase boundaries, subagent reporting contracts, and per-phase verification checklists.

How do I verify allowed APIs and methods before orchestrating multi-step task execution?▼

Verify allowed APIs by executing a mandatory Phase 0 documentation discovery step. This establishes an allowed-APIs list with sources and subagent reporting contracts, ensuring orchestrator-led execution relies on verified signatures rather than assumptions.

Does this phased planning approach work for feature planning in new chat contexts?▼

Yes, this phased planning approach works for feature planning in new chat contexts. It is specifically designed for pre-execution design where APIs and signatures must be verified, generating LLM-executable plans with copy-from-docs instructions.

What are the limitations of relying on LLM-generated implementation plans without documentation discovery?▼

Without documentation discovery, LLM-generated implementation plans risk hallucinating APIs and undocumented parameters. This skill mitigates that limitation by enforcing evidence-based verification checklists and explicit anti-pattern guards against invented parameters.

Related Skills

Explore More Software Engineering Skills→
chicago-joechicago-joe

make-plan

Plan feature implementations in phased, executable steps with documentation discovery.

Community
Advanced
ryanthedevryanthedev
351

building

Orchestrate gated multi-phase plan execution from discovery to working code.

Community
Advanced
masrurimzmasrurimz

doc-writer

Generate JSDoc/TSDoc comments, READMEs, and API documentation across codebases.

Community
Basic
rodrigobranasrodrigobranas
1

cy-create-tasks

Break down PRDs and TechSpecs into granular task files with codebase context.

Community
Advanced