What does the fpf:actualize command do?

It compares your current repository state with a saved baseline to find changes that might make your documented evidence, decisions, or project context outdated.

What is Epistemic Debt in this context?

Epistemic debt refers to the gap between the documented state of your project and the actual reality of the code, which occurs when changes are made without updating the corresponding evidence or context.

How does it know which evidence is stale?

The skill reads evidence files in the .fpf/evidence/ directory and checks the carrier_ref field; if the files referenced there have changed in git, the evidence is flagged as stale.

When is the best time to run the actualize skill?

It is best used before starting new work, after significant code changes, or as part of a weekly maintenance routine to ensure your AI agent has accurate project context.

FPF Knowledge Base Sync

Name: FPF Knowledge Base Sync
Author: NeoLabHQ

byNeoLabHQ

•

687

•

Productivity & Workflow

Reconciles the project's FPF knowledge base with recent repository changes to eliminate epistemic debt and context drift.

FPF Knowledge Base Sync (actualize) is a specialized maintenance tool for the context-engineering-kit designed to keep your assurance case in sync with your evolving codebase. By performing a structured three-part audit against git changes, it identifies drift in project configuration, flags stale evidence linked to modified files, and highlights architectural decisions that may require re-evaluation. This ensures that your AI agent operates on a living, accurate representation of the project rather than outdated documentation, effectively managing the epistemic debt that accumulates during rapid development cycles.

Key Features

01Automated git-based change detection since the last known baseline

02Context drift analysis for configuration files like package.json and Dockerfiles

03687 GitHub stars

04Decision Record Report (DRR) relevance auditing based on foundational file changes

05Evidence staleness tracking by cross-referencing carrier_ref fields with git diffs

06Structured reporting with actionable steps for re-validating evidence and hypotheses

Use Cases

01Validating project context before starting a new development sprint or task

02Maintaining a high-integrity assurance case for security-critical or complex systems

03Synchronizing documentation and evidence after major refactors or dependency updates

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add neolabhq/context-engineering-kit actualize

For use in Claude.ai and ChatGPT

Download Skill