update-docs

Reconcile planned work with actual outcomes and update documentation artifacts.

Updated Feb 3, 2026

Search Tags:#planning #documentation #drift #update #session-wrap #work-ledger #as-built

Ready to run

npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill update-docs-bedabeda-growth

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-docs
Source: https://github.com/BedaBeda-Growth/bedabeda-growth-site/tree/main/skills/update-docs
Command: npx skills add https://github.com/BedaBeda-Growth/bedabeda-growth-site --skill update-docs-bedabeda-growth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reconcile planned work with actual outcomes after a session and update all affected artifacts to reflect reality, ensuring documentation stays aligned with implementation.

Core Features & Use Cases

Reconstruct the actual work completed from the discussion and artifacts.
Identify and surface outdated or conflicting docs, plans, and decisions.
Update the work ledger, plans, and related artifacts with precise as-built notes.

Quick Start

Run this skill at the end of a session to generate an as-built record and update the work ledger.

Frequently Asked Questions about update-docs

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

FAQPage Schema

How do I close documentation drift between what was planned and what I actually built?▼

To close documentation drift, you need to reconcile actual session outcomes with original plans and update affected artifacts in place. This process reconstructs completed actions, identifies stale documents, and appends precise as-built notes to preserve original intent.

What is the best way to update stale plans and decisions after a work session?▼

Updating stale plans after a work session involves reconstructing actual work from discussion and artifacts, then updating the work ledger with precise as-built notes. This ensures plans, architecture, and implementation docs accurately reflect reality.

How do I generate an as-built record for a completed work session?▼

Generating an as-built record requires running a session wrap-up that reconciles planned work with actual outcomes. It guides you through rebuilding the narrative, closing work ledger gaps, and appending notes while preserving original intent.

Can I update architecture and code documentation at the end of any work session?▼

Yes, you can update architecture and code documentation at the end of any session by reconciling actual outcomes with original plans. This ensures all affected artifacts reflect reality and closes gaps across implementation and documentation.

Why does my work ledger have gaps between planned work and actual implementation?▼

Work ledger gaps occur when actual implementation diverges from original plans without updating documentation. Reconciling session outcomes and appending precise as-built notes closes these gaps while preserving original intent.

When do I need to reconcile planned work with actual outcomes?▼

You need to reconcile planned work with actual outcomes at the end of any work session. This ensures documentation stays aligned with implementation by identifying stale artifacts and updating plans, decisions, and as-built notes.