quick-reconcile

Closes out directly delivered master-plan slices by updating receipts, docs, and running checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a master-plan slice is implemented directly via a quick brief without a focused Plan, there is no structured closeout: canonical docs drift, delivery evidence is lost, and temporary workflow artifacts linger. This Skill performs the mandatory closeout for that direct delivery route. ## Core Features & Use Cases - Slice Receipt Management: Writes exactly one row to the master plan's Slice delivery receipts table, recording route, state, and evidence with strict acceptance-state rules. - Canonical Doc Updates: Synchronizes reference documentation when a slice changes user-visible capabilities, APIs, data models, or conventions, then regenerates generated indexes via check_docs.py. - Full Gate Verification: Runs stage_check.py and doc checks, applying bounded regression-repair policy without weakening checks or broadening scope. - Artifact Cleanup: Removes redundant Plans created for already-delivered atomic slices while preserving Plans with real history. - Use Case: After a quick-executor ships slice MP-03 and its focused check passes, run this Skill to record the receipt, update docs, verify all gates, and delete the redundant Plan directory. ## Quick Start Close out master-plan slice MP-03 delivered by the quick route using its brief, executor report, and passing focused check.

Frequently Asked Questions about quick-reconcile

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

FAQPage Schema
How do I close out a master-plan slice delivered without a Plan?▼

Run the quick-reconcile workflow with the master-plan path, slice ID, quick brief, executor report, changed paths, and focused-check result. It writes one receipt row, updates canonical docs, runs full checks, and removes redundant artifacts.

When should I use quick reconcile instead of full reconcile?▼

Use quick reconcile only for atomic slices delivered directly through a quick brief with no focused Plan. If the slice went through a staged Plan with work orders, use the full reconcile route, which writes a Plan-route receipt instead.

Can automated checks mark a slice as Accepted?▼

No. Automated checks can only write 'Implemented; awaiting human acceptance'. The 'Accepted YYYY-MM-DD' state requires explicit human acceptance of the slice's UX gate, and dependent slices only treat accepted receipts as satisfied prerequisites.

What happens if the quick implementation failed or scope widened?▼

Quick reconcile stops and creates a focused Plan carrying the report's evidence instead of laundering the work. The same applies when full checks reveal a non-atomic repair or a human rejects the delivered result.

Does quick reconcile commit changes automatically?▼

No. Unlike full reconcile, it never commits automatically because it may run amid unrelated user work. It commits only when the user explicitly asks, staging just the direct slice and closeout paths.