make-plan

Create phased implementation plans using documentation discovery and API identification.

1|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/JerryGanst/qiduandebug --skill make-plan-jerryganst
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: make-plan
Source: https://github.com/JerryGanst/qiduandebug/tree/main/plugin/skills/make-plan
Command: npx skills add https://github.com/JerryGanst/qiduandebug --skill make-plan-jerryganst

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of detailed, phased implementation plans, ensuring that tasks are well-defined and executable, especially before initiating automated execution.

Core Features & Use Cases

  • Phased Planning: Generates LLM-friendly plans broken down into sequential phases.
  • Documentation Discovery: Prioritizes finding and utilizing existing documentation and API patterns.
  • Delegation Model: Employs subagents for fact-gathering and extraction, with the orchestrator handling synthesis and plan authoring.
  • Use Case: When tasked with planning a new feature implementation, this Skill will first discover relevant documentation, identify available APIs, and then construct a step-by-step plan for development.

Quick Start

Use the make-plan skill to create a phased implementation plan for adding user authentication.

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 for a new software feature?

To create a phased implementation plan, you need to discover relevant documentation and identify available APIs first, then construct a step-by-step sequential plan for development before execution begins.

What is the best way to orchestrate task management for multi-step software development?

Orchestrating task management for multi-step development is best handled by employing a delegation model with subagents for fact-gathering and an orchestrator for plan synthesis and authoring.

Does automated implementation planning work with existing project documentation?

Automated implementation planning works directly with existing project documentation by prioritizing documentation discovery and API identification to ensure tasks are well-defined.

Why do I need to discover APIs before generating an implementation plan?

You need to discover APIs before generating an implementation plan because identifying available API patterns ensures the resulting development steps are executable and properly aligned with existing systems.

Can I use subagents to gather facts for software implementation plans?

You can use subagents to gather facts and extract relevant information, allowing a central orchestrator to handle the synthesis and authoring of the final phased implementation plan.