master-plan

Creates detailed master plan documents that split broad product destinations into reviewable slices.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/skyrocoster/dnd-kids-resources --skill master-plan-skyrocoster
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: master-plan
Source: https://github.com/skyrocoster/dnd-kids-resources/tree/main/.opencode/skills/master-plan
Command: npx skills add https://github.com/skyrocoster/dnd-kids-resources --skill master-plan-skyrocoster

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large cross-cutting product redesigns and multi-feature initiatives lack a shared, concrete destination, causing teams to jump into implementation without aligned decisions or a way to divide work into independently reviewable pieces. ## Core Features & Use Cases - Destination Definition: Writes or refines a master plan document under docs/master-plans/ using the repository template, recording decisions rather than implementation status. - Decision Facilitation: Resolves product decisions one at a time with the user, offering three concrete choices with a marked recommendation and supporting evidence. - Slice Decomposition: Splits the destination into small slices, each with a clear human-visible result and a clear human-doable action, plus ASCII mockups for UI composition and interaction states. - Use Case: When planning a ground-up redesign of a campaign manager UI, use this Skill to produce a master plan that records layout decisions, constraints, and acceptance criteria, then hands off individual slices for focused execution plans. ## Quick Start Ask the assistant to create a master plan for your broad product goal, for example by saying create a master plan for redesigning the dungeon map editor experience.

Frequently Asked Questions about master-plan

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

FAQPage Schema
How do I create a master plan for a large product redesign?▼

Invoke the master-plan skill with your broad destination. It reads the repository docs and template, resolves decisions with you one at a time, then writes a detailed document under docs/master-plans/ split into small reviewable slices.

What is the difference between a master plan and an execution plan?▼

A master plan is broader than an execution plan and more detailed than a design principle. It records product decisions and slice definitions, while execution plans handle the focused implementation of a single selected slice.

Does the master-plan skill write implementation code?▼

No. The skill explicitly produces no implementation code, work orders, or active queue status. Implementation begins only when a user selects a slice and a separate routing step verifies prerequisites.

How are slices in a master plan structured?▼

Each slice delivers one specifically scoped feature with a clear human-visible result and a clear human-doable action. Slices must be independently judgeable and require human acceptance after delivery.

When should I not use a master plan?▼

Avoid it for small, single-feature changes that fit directly into a focused execution plan. Master plans suit broad destinations spanning multiple features or cross-cutting redesigns that need decision alignment first.