make-plan

Create phased execution plans with subagent orchestration and documentation discovery.

Updated Jun 19, 2026

Search Tags:#planning #documentation #subagents #plan #orchestrator #phases

Ready to run

npx skills add https://github.com/Intelligent-Resourcing-Team-Environment/claude-memory --skill make-plan-intelligent-resourcing-team-environment

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: make-plan
Source: https://github.com/Intelligent-Resourcing-Team-Environment/claude-memory/tree/main/plugin/skills/make-plan
Command: npx skills add https://github.com/Intelligent-Resourcing-Team-Environment/claude-memory --skill make-plan-intelligent-resourcing-team-environment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured approach to planning features and tasks by orchestrating phased work with documentation discovery and explicit phase boundaries.

Core Features & Use Cases

Create phased, execution-ready plans suitable for handoffs in multi-context environments.
Leverage subagents for evidence gathering, documentation references, and verification checks.
Use for feature rollouts, complex refactors, and cross-team initiatives requiring clear phase delineation.

Quick Start

Plan a feature with phased steps and documentation references.

Frequently Asked Questions about make-plan

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

FAQPage Schema

How do I create phased execution plans for complex feature rollouts?▼

Phased execution plans for feature rollouts are created by orchestrating subagents and discovering documentation. This approach enforces phase boundaries, evidence-backed decisions, and a subagent reporting contract to ensure plans are traceable and testable.

What is documentation discovery in feature planning and when do I need it?▼

Documentation discovery in feature planning is a Phase 0 process that gathers references and evidence before execution begins. You need it when planning complex initiatives or cross-team refactors that require traceable, evidence-backed decisions and clear phase delineation.

How do I use subagents to gather evidence for multi-task planning?▼

Subagents gather evidence for multi-task planning by operating under a Subagent Reporting Contract that structures their outputs. They handle documentation references and verification checks, providing the evidence needed for execution-ready plans suitable for multi-context handoffs.

Does this planning approach work for cross-team initiatives requiring clear handoffs?▼

Yes, this planning approach works for cross-team initiatives by producing structured phase outputs and explicit phase boundaries. It supports multi-context environments by ensuring plans are execution-ready, traceable, and testable across different teams.

What's the best way to structure phased plans for complex refactors?▼

The best way to structure phased plans for complex refactors is enforcing a Phase 0 documentation discovery step followed by structured phase outputs. This ensures traceable, testable plans with evidence-backed decisions and clear delineation between each phase boundary.

When should I not use a phased planning approach for my tasks?▼

You should not use a phased planning approach for simple, single-step tasks that lack complex dependencies. It is designed for multi-task undertakings and feature rollouts that benefit from phase boundaries, subagent orchestration, and evidence-backed documentation discovery.