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

implement-order

Executes one canonical work order from a checked order artifact with bounded file edits and proofs.

Updated Mar 24, 2026
Search Tags:#workflow automation#code implementation#work order#bounded execution#proof commands#authorization scope
One-click install
npx skills add https://github.com/skyrocoster/dnd-kids-resources --skill implement-order-skyrocoster
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-order
Source: https://github.com/skyrocoster/dnd-kids-resources/tree/main/.opencode/skills/implement-order
Command: npx skills add https://github.com/skyrocoster/dnd-kids-resources --skill implement-order-skyrocoster

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents uncontrolled code changes by constraining execution to a single reviewed work order, ensuring only authorized files are touched and every change is verified by declared proof commands. ## Core Features & Use Cases - Bounded Execution: Reads only declared context paths and modifies only files listed in the order's authorization block. - Ordered Proof Verification: Runs each exact proof command from its declared working directory, with at most one in-scope repair attempt on failure. - Structured Result Reporting: Records STATUS, proof results, dirty paths, authorization audits, and escalations in the order artifact. - Use Case: A team lead hands you a checked order from docs/plans/active/<feature>/orders/; you execute exactly that order's file actions and proofs, then report DONE, FAILED, or BLOCKED without starting adjacent work. ## Quick Start Execute the checked work order at docs/plans/active/my-feature/orders/001.md exactly as written and report the result.

Frequently Asked Questions about implement-order

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

FAQPage Schema
How do I execute a work order without changing unauthorized files?▼

Read the order's canonical JSON packet and modify only paths listed under authorization.creates, authorization.edits, and authorization.removes. Context paths are read-only, and explicit non-file actions never authorize file changes.

What is a canonical work order in a docs/plans/active workflow?▼

It is a checked order artifact containing an immutable JSON packet with known_facts, context paths, authorization scopes, ordered actions, proof commands, and escalation boundaries. The executor treats it as the compile envelope and does not redesign it.

What happens when a proof command fails during order execution?▼

Make at most one in-scope repair and rerun the failed proof once. If it still fails, escalate at the packet's escalate_if boundaries and record the result as FAILED or BLOCKED rather than widening the order.

Can I run extra verification checks beyond the declared proofs?▼

No. Run each exact proof command in order from its declared cwd and do not synthesize extra checks. Helper scripts like new_order.py and check_orders.py are invoke-only and cannot be modified.

When should I not use a single-order execution approach?▼

Avoid it when the task requires exploratory design, multi-order coordination, or re-deriving facts, since the skill forbids redesigning, adding paths, or starting adjacent work. One order per context is the hard limit.

Related Skills

Explore More Software Engineering Skills→
rickyanandarickyananda
1

design-md

Create and validate DESIGN.md specification files with YAML front matter and WCAG contrast checks.

Community
Advanced
tonysyutonysyu
2

openspec-continue-change

Generate the next OpenSpec workflow artifact using the OpenSpec CLI.

Community
Advanced
eygrabereygraber
1

check

Run formatting, detekt, lint, and unit tests on Android and Kotlin projects.

Community
Intermediate
ruskicoderruskicoder
3

pair-programming

Guides interactive pair programming by proposing code changes and applying edits only on explicit confirmation.

Community
Intermediate