skills.rest
skyrocoster
skyrocosterCOMMUNITY
Explore all skills by this author →
GitHub

create-plan

Creates a focused human-readable implementation Plan under docs/plans/active/ for one concrete feature.

Updated Mar 24, 2026
Search Tags:#planning#documentation#markdown#agent workflow#work orders#feature plan#stage decomposition
One-click install
npx skills add https://github.com/skyrocoster/dnd-kids-resources --skill create-plan-skyrocoster
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-plan
Source: https://github.com/skyrocoster/dnd-kids-resources/tree/main/.opencode/skills/create-plan
Command: npx skills add https://github.com/skyrocoster/dnd-kids-resources --skill create-plan-skyrocoster

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns a vague feature request into a single bounded, human-readable Plan document that settles contracts, stages, and routing decisions before any implementation code is written. ## Core Features & Use Cases - Focused Plan Authoring: Writes one Plan per concrete outcome to docs/plans/active/<feature>/<feature>.md using the Layer 1 schema in docs/PLAN_TEMPLATE.md. - Stage Decomposition & Routing: Breaks the outcome into coherent stages and routes each as quick work, work-ordered via to-orders, or human-decision work. - Evidence Discipline: Delegates bounded repository retrieval to explore-deepseek and records verified planning byproducts for downstream compilation. - Use Case: When asked to "plan this feature", the agent reads the docs manifest and owning area guides, settles contracts, and produces a one-screen Plan ready for to-orders. ## Quick Start Ask the agent to create a plan for your feature, for example: create a plan for adding quest filtering to the campaign manager.

Frequently Asked Questions about create-plan

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

FAQPage Schema
How do I create an implementation plan for a new feature?▼

Invoke the create-plan skill with a concrete feature request. It reads the docs manifest and area guides, settles contracts, breaks the outcome into stages, and writes a Plan to docs/plans/active/<feature>/<feature>.md without writing code.

What is the difference between create-plan, to-plan, and master-plan?▼

Use create-plan for one bounded feature Plan. If the work derives from a slice under docs/master-plans/, use to-plan instead. If the request is broad enough to need several focused Plans, run master-plan first.

Where are plan files stored and what format do they use?▼

Plans live at docs/plans/active/<feature>/<feature>.md and follow the Layer 1 schema in docs/PLAN_TEMPLATE.md, including Status, Areas, Read trigger, and a Touches section with repo-root-relative globs.

Does create-plan write implementation code or work orders?▼

No. It produces only the human-readable Plan and optional planning byproducts. Work orders are generated afterward by running to-orders for each work-ordered stage.

When should I not create a new plan?▼

Do not create a Plan if an active Plan already covers the outcome; update or continue that Plan instead. Also avoid creating one when the request spans multiple outcomes requiring a master plan first.

Related Skills

Explore More Software Engineering Skills→
nholder88nholder88
2

draft-repo-readme

Draft a README from a repository's source files and commit history.

Community
Intermediate
SentioLabsSentioLabs
1

arc-plan

Convert approved Arc plans into ordered tracked work via arc-issue-tracker.

Official
Intermediate
Zedong-LiuZedong-Liu
21

claude-deepseek-sidecar

Delegates bounded tasks to DeepSeek worker agents through Claude Code.

Community
Basic
loianeloiane
50

epic-slicing-planning

Plan Epic-level architecture and vertical-slice roadmaps for large features.

Community
Advanced