to-plan

Routes one selected master-plan slice to direct execution or a focused Plan.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working from a master plan, teams waste effort deciding whether each slice needs a full planning document or can go straight to implementation. This Skill removes that ambiguity by autonomously routing exactly one selected slice to the smallest safe execution path. ## Core Features & Use Cases - Autonomous routing gate: Evaluates prerequisites, settled behavior, atomicity, and coordination needs to choose between direct quick-executor delivery and a focused Plan, without asking the user to decide. - Focused Plan creation: Generates a Plan in docs/plans/active/ following the repository's PLAN_TEMPLATE, preserving human outcomes, acceptance scripts, dependencies, and stop conditions. - Compact subagent handoff: Returns a structured RESULT/ROUTE/ARTIFACT/NEXT summary so the coordinator needs no additional repository reads. - Use Case: A user selects slice S3 from docs/master-plans/ and says "to plan"; the Skill verifies prerequisites are accepted, finds the slice is atomic with settled UX, dispatches quick-executor directly, and hands the result to quick-reconcile. ## Quick Start Select a slice from a master plan in docs/master-plans/ and ask the assistant to route it to plan for implementation.

Frequently Asked Questions about to-plan

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

FAQPage Schema
How do I implement one slice from a master plan?▼

Name the master plan and the slice ID, then invoke this routing workflow. It reads the master plan, verifies prerequisite acceptance, and either dispatches direct execution or creates a focused Plan under docs/plans/active/.

When does a master-plan slice need a full Plan document?▼

A Plan is created when any routing condition is unproven: unsettled behavior or UX, unresolved design or API decisions, non-atomic implementation, or a need for durable coordination while queued or delegated. Small file count alone does not qualify for direct delivery.

Can a slice skip planning and go straight to implementation?▼

Yes, if every gate condition holds: accepted prerequisites, settled product behavior and ownership, one atomic change, verifiable authorized paths, and no remaining design decisions. The Skill then writes an ephemeral brief and dispatches quick-executor.

What happens if direct execution of a slice fails?▼

The executor's evidence is preserved and a focused Plan is created instead. The brief is never widened or repaired in place, and the failed routing criterion is recorded in the Plan's compiler handoff.

Does this workflow start dependent slices automatically?▼

No. Every route stops at the selected slice's human acceptance gate. Dependent slices with unaccepted prerequisites are never started, and only one Plan is created per run.