What problem does it solve?
As a codebase evolves, the FPF knowledge base (.fpf/) drifts out of sync: evidence files reference changed code, decisions rest on stale foundations, and project context no longer matches reality. This Skill audits recent git changes against the knowledge base to surface context drift, stale evidence, and outdated decisions before they corrupt downstream reasoning.
Core Features & Use Cases
- Context Drift Detection: Compares changed configuration files (package.json, Dockerfile, go.mod, etc.) against
.fpf/context.md and prompts updates.
- Evidence Staleness Audit: Cross-references
carrier_ref fields in .fpf/evidence/ files with git diffs to flag stale evidence and affected hypotheses.
- Decision Relevance Review: Traces DRR files in
.fpf/decisions/ back to source evidence and flags potentially outdated decisions.
- Baseline Tracking: Maintains a
.fpf/.baseline file recording the last actualized commit for incremental audits.
- Use Case: Before starting a new sprint, run the actualization audit to discover that three evidence files reference a refactored API handler, then re-validate those hypotheses before making architecture decisions.
Quick Start
Ask the agent to actualize the FPF knowledge base against recent git changes and report any stale evidence or outdated decisions.