All products

Reconcile project records with AI

Update the records that should reflect a proven outcome. Preserve historical evidence, avoid duplicate entries and report what remains inaccessible or unverified.

Reconcile project records with AI after the work has happened but the surrounding documents still show an older state. The work-closeout skill checks evidence of the change, identifies which records are authoritative now and updates only claims made stale by the outcome. Historical notes and raw evidence stay intact.

A delivered draft and an accepted deliverable are different milestones. A receipt may prove the former without establishing the latter. The workflow can update a current handover reference, leave an unproven status open and record why a remote tracker could not be changed or verified.

What it does

  • Identify current documents affected by a proven change.
  • Distinguish raw evidence from editable project records.
  • Check for existing entries before adding another.
  • Verify local changes against the original outcome.
  • Record inaccessible or ambiguous surfaces as unresolved.

Install and use

  1. Install the skill in a file-aware agent and supply the evidence, authorised roots and routing rules. The optional local inventory helper uses Python 3. External changes require their own authority and readback.
  2. Ask, “Reconcile this confirmed handover with our current project notes. Preserve the original receipt and leave customer acceptance open.”
  3. Read the changed records and the remaining blockers before treating closeout as complete.

FAQ

Source

Made by Jarad Johnson. Original skill: work-closeout, published on GitHub under the MIT licence.

View on GitHub