to-orders

Compile a settled Plan stage into canonical JSON work-order packets and artifacts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved plan stage into executable work often loses critical details like dependencies, authorization boundaries, and proof commands. This Skill compiles one settled Plan stage into lossless, canonical work-order packets so executors receive exact, unambiguous instructions. ## Core Features & Use Cases - Packet Compilation: Builds one JSON packet per approved order matching the docs/PLAN_TEMPLATE.md structure, covering identity, dependencies, authorized edits, context inputs, and ordered actions. - Proof and Acceptance Definition: Records exact proof commands with working directories, plus coordinator and validator acceptance criteria, exclusions, and escalation boundaries. - Validation Workflow: Invokes scripts/new_order.py to render orders and scripts/check_orders.py to verify them, with semantic review required beyond checker success. - Use Case: After a feature plan stage is approved, use this Skill to split it into executor-ready orders under docs/plans/active/<feature>/orders/ with exact file authorizations and verification commands. ## Quick Start Compile the approved plan stage for my feature into canonical work-order packets and validate them with the order checker.

Frequently Asked Questions about to-orders

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

FAQPage Schema
How do I convert a plan stage into executable work orders?▼

Compile each approved order into a JSON packet matching docs/PLAN_TEMPLATE.md, then run scripts/new_order.py with the packet and validate the result with scripts/check_orders.py. Review the rendered order semantically, since checker success alone is not sufficient.

When should a plan stage be split into multiple work orders?▼

Split only at genuine independent or sequential executor boundaries, never because of file or action counts. A one-order plan is valid when the stage has no real executor separation.

What must a canonical work-order packet contain?▼

Each packet needs an exact output path, identity and dependency paths with strength rationale, authorized creates/edits/removes, bounded context inputs, settled facts, ordered actions, exact proof commands, acceptance criteria, exclusions, and escalation boundaries.

Can I dispatch or implement orders while compiling them?▼

No. Compiling, dispatching, and implementing are separate lifecycle phases. Only proceed to dispatch or implementation when a separate workflow explicitly authorizes that step.

Are there size limits on generated work orders?▼

There are no mechanical size caps on orders. Coherence is reviewed by the frontier instead, so packets should preserve exact details rather than compress or infer content.