reconcile

Closes out completed work orders by updating plans, running checks, and committing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a stage's work orders finish, project documentation drifts out of sync with what actually shipped, and spent order files clutter the repo. This Skill performs the documentation closeout: it collapses completed orders into the Plan's Shipped table, updates canonical references, runs the full check suites, deletes spent orders, and commits everything in one consistent commit. ## Core Features & Use Cases - Order Collapse and Triage: Confirms each DONE order actually landed, folds it into the Plan's Shipped table, and diagnoses FAILED or BLOCKED orders with reissued corrective orders carrying failure knowledge forward. - Documentation Synchronization: Updates canonical references (API_REFERENCE.md, DATA_MODEL.md, ARCHITECTURE.md) only when real contracts changed, regenerates derived indexes via check_docs.py, and updates linked master-plan slice receipts. - Gated Commit: Runs stage_check.py and check_docs.py before committing the whole worktree in one commit, with automatic regression repair via scout and quick-executor subagents. - Use Case: After executors finish all work orders for a feature stage, invoke this Skill to reconcile the shipped work into durable docs, archive the Plan when the feature completes, and produce a single green commit. ## Quick Start Ask the agent to reconcile the finished stage for your feature, for example by saying "reconcile the stage now that all orders are done".

Frequently Asked Questions about reconcile

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

FAQPage Schema
How do I close out completed work orders in a plan-based workflow?▼

Run the reconcile skill after all of a stage's work orders are marked DONE. It verifies each order landed, collapses them into the Plan's Shipped table, runs the full check suites, deletes spent order files, and commits everything in one commit.

What happens when a work order is FAILED or BLOCKED at closeout?▼

The reconcile agent reads the order's EXECUTOR RESULT and dirty files first, then diagnoses the failure. Small obvious fixes become corrected reissued orders carrying the failure evidence forward; mis-scoped orders are split or rewritten, and Plan-level problems escalate to the user.

Does reconcile modify source code during closeout?▼

Only in a narrow direct-repair case: the fix must be fully determined by existing evidence, require zero exploration, be small and mechanical, and be verifiable by re-running the failed check. Larger regressions go through scout evidence gathering and a quick-executor brief, or become corrective work orders.

When does reconcile update canonical documentation like API_REFERENCE.md?▼

Only when shipped work changed a real contract such as an API shape, data model, architecture convention, design token, or testing contract. Generated sections are refreshed with check_docs.py --write-generated rather than hand-edited, and unchanged contracts are recorded as such.

Why does reconcile refuse to commit when checks fail?▼

A reconcile commit represents a fully consistent repo state, so stage_check.py and check_docs.py --check must both pass first. Committing on red would record an unreconciled stage; failures are fixed or reissued as orders before any commit happens.