Reconcile

Align VISION.md, SPEC.md, and BUILDING.md to reflect current project reality.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/eddiebelaval/triad --skill reconcile-eddiebelaval
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Reconcile
Source: https://github.com/eddiebelaval/triad/tree/main/skills/reconcile
Command: npx skills add https://github.com/eddiebelaval/triad --skill reconcile-eddiebelaval

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reconcile automates alignment of Triad documents (VISION.md, SPEC.md, BUILDING.md) so your current reality is always reflected in strategy and execution.

Core Features & Use Cases

  • Conversational interview-driven updates that rewrite VISION and SPEC based on new insights or changes in the project.
  • Automated detection of drift between documents and generation of actionable reconciliation steps.
  • Lightweight governance flow that initializes the triangle, surfaces gaps, and maintains Evolution and Drift logs.

Quick Start

Run the reconcile process to scan the project, then rewrite VISION and SPEC to reflect the current reality.

Frequently Asked Questions about Reconcile

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

FAQPage Schema
How do I keep project vision and spec documents aligned with current development reality?

Triad document alignment is maintained by scanning VISION.md, SPEC.md, and BUILDING.md to detect drift, then applying conversation-driven updates that rewrite strategy and execution docs to reflect the current project reality.

What is the best way to detect drift between project specification and building documents?

Drift detection between specification and building documents is automated by scanning the Triad files for inconsistencies, generating actionable reconciliation steps, and logging the detected gaps in a dedicated Drift log for review.

How do I initialize VISION, SPEC, and BUILDING markdown files for a new project?

Initializing VISION, SPEC, and BUILDING markdown files requires running a governance flow that sets up the document triad, enforces structured frontmatter, and establishes Evolution and Drift logs to track future project changes.

Can I update project strategy documents through a conversational interview process?

Updating project strategy documents through a conversational interview is supported, allowing new insights and project changes to directly rewrite VISION.md and SPEC.md while maintaining alignment with BUILDING.md.

Does the reconciliation process require any external dependencies or components?

The reconciliation process requires no external dependencies or components, operating entirely on the Triad markdown documents with optional support for on-demand resources stored under scripts/, references/, and assets/ directories.

When should I not use an automated triad document reconciliation approach?

Automated triad document reconciliation should not be used when a project lacks the VISION.md, SPEC.md, and BUILDING.md file structure, as the enforcement of structured frontmatter and drift logs depends on this specific governance format.