make-plan

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

Updated Jun 2, 2026

Search Tags:#planning #documentation #verification #feature-planning #cross-team #phased-approach

Ready to run

npx skills add https://github.com/chicago-joe/manymems --skill make-plan-chicago-joe

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: make-plan
Source: https://github.com/chicago-joe/manymems/tree/main/plugin/skills/make-plan
Command: npx skills add https://github.com/chicago-joe/manymems --skill make-plan-chicago-joe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning complex features with explicit phases and documentation helps teams avoid scope creep and misalignment by ensuring outputs are structured and reviewable.

Core Features & Use Cases

Phase 0: Documentation Discovery (ALWAYS FIRST) — deploy subagents to read documentation, identify APIs, and compile a cited set of references.
Phase-based Implementation — break work into concrete, check-pointed phases with task framing and evidence references.
Mandatory Subagent Reporting Contract — require sources consulted, concrete findings, snippet-ready locations, and a confidence assessment.
Verification & Anti-pattern Guards — ensure alignment with docs, surface invalid patterns, and provide verification steps.
Final Verification — confirm implementation matches the documentation, run checks, and close the plan.

Quick Start

Use this skill to generate a phased, implementation plan by first discovering relevant docs and then outlining concrete phases with references.

Frequently Asked Questions about make-plan

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

FAQPage Schema

How do I plan a complex feature implementation across multiple teams?▼

Feature implementation planning uses a documentation-first discovery approach to break complex cross-team engineering tasks into concrete, check-pointed phases with evidence references and traceable decisions.

What is a documentation-first phased approach for feature planning?▼

A documentation-first phased approach deploys subagents to read documentation, identify APIs, and compile a cited set of references before outlining concrete implementation phases with mandatory reporting.

How do I enforce documentation alignment during a multi-step migration?▼

Enforce documentation alignment during migrations by applying verification checks and anti-pattern guards that surface invalid patterns, ensuring the implementation matches the referenced docs.

What is a subagent reporting contract for feature planning?▼

A subagent reporting contract requires sources consulted, concrete findings, snippet-ready locations, and a confidence assessment to ensure traceable decisions during phase-based implementation.

Can I use this phased planning approach for multi-step product migrations?▼

Yes, this phased planning approach applies to multi-step migrations and product initiatives across teams, providing phase boundaries, evidence gathering, and structured verification checks.