reconcile

Reconcile scaffolding documents against the actual codebase to eliminate drift.

Updated May 24, 2026
One-click install
npx skills add https://github.com/RCSnyder/lights-out-swe-plugin --skill reconcile-rcsnyder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reconcile
Source: https://github.com/RCSnyder/lights-out-swe-plugin/tree/main/skills/reconcile
Command: npx skills add https://github.com/RCSnyder/lights-out-swe-plugin --skill reconcile-rcsnyder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents wasted effort and broken approvals by detecting when the pipeline’s scaffolding documents have drifted from the actual codebase.

Core Features & Use Cases

  • Cross-checks key artifacts: directory structure, interfaces, acceptance criteria, external integrations, stack/deploy config, log accuracy, and readiness/traceability.
  • Auto-fixes drift: resolves cosmetic and structural mismatches so the repo reflects the intended plan.
  • Flags spec-violating drift: highlights cases where the scaffolding no longer matches real behavior for explicit human review.
  • Use case: after REVIEW and before VERIFY, a maintainer can reconcile scaffolding after code changes to ensure the next gate will be meaningful.

Quick Start

Run the Lights Out SWE: Reconcile agent to reconcile scope.md, design.md, readiness.md, log.md, and related scaffolding with your current codebase.

Frequently Asked Questions about reconcile

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

FAQPage Schema
How do I keep scaffolding documents in sync with my codebase after manual edits?

Scaffolding reconciliation cross-checks artifacts like scope.md and design.md against the actual codebase to detect drift. It auto-fixes cosmetic and structural mismatches while flagging spec-violating changes for explicit human review.

What is scaffolding drift and when do I need to reconcile spec traceability?

Scaffolding drift occurs when planned behavior documents no longer match the codebase. You need to reconcile spec traceability after design reviews, session resumes, blocked-to-unblocked cycles, or manual code edits to ensure pipeline approvals remain valid.

How do I validate directory structure and interfaces against acceptance criteria?

Validating directory structure and interfaces against acceptance criteria is done through seven reconciliation axes. This process verifies external integrations, stack/deploy configuration, log accuracy, and readiness to correct structural mismatches automatically.

Does the reconciliation process require any external dependencies to run?

The reconciliation process requires no external dependencies to run. It operates directly within software-engineering agent workflows to validate and correct deployment configuration, log accuracy, and readiness documents against the current repository state.

Can I use scaffolding reconciliation to fix broken approvals before the VERIFY phase?

You can use scaffolding reconciliation to fix broken approvals before the VERIFY phase. Running it after REVIEW resolves mismatches in readiness.md and related documents, ensuring the next verification gate evaluates meaningful and accurate specifications.

What are the limitations of auto-fixing code drift in scaffolding documents?

Auto-fixing code drift is limited to cosmetic and structural mismatches. When scaffolding no longer matches real behavior or violates specifications, the process highlights these cases instead of auto-fixing them, requiring explicit human review before proceeding.