fpf:status

Display FPF knowledge base status with hypothesis counts, evidence freshness, and decision records.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/luicabref97/sushi-jungle-web --skill fpf-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fpf:status
Source: https://github.com/luicabref97/sushi-jungle-web/tree/main/.agents/skills/fpf-status
Command: npx skills add https://github.com/luicabref97/sushi-jungle-web --skill fpf-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the manual and error-prone task of auditing an FPF knowledge base by verifying directory structure, counting hypotheses by layer, checking evidence freshness, and summarizing recent decisions so maintainers can immediately understand system health.

Core Features & Use Cases

  • Directory Verification: Confirms the presence of .fpf and required subdirectories (knowledge L0/L1/L2, evidence, decisions).
  • Hypothesis Counts & Phase Detection: Counts files in each knowledge layer and infers the current FPF phase using the provided phase detection logic.
  • Evidence Freshness Analysis: Parses evidence frontmatter valid_until fields to classify items as fresh, stale, or expired and surfaces warnings.
  • Decision Summary: Lists decision records and recent DRRs to indicate completed decisions and winners.
  • Use Case: A knowledge manager or engineer uses this Skill to prepare the knowledge base for audits, decide next workflow steps, or identify stale evidence needing review.

Quick Start

Run the fpf:status skill to display the FPF knowledge base directory structure, hypothesis counts, evidence freshness classification, and recent decisions summary.

Frequently Asked Questions about fpf:status

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

FAQPage Schema
How do I check the status of an FPF knowledge base?

Check FPF knowledge base status by reading the .fpf directory to count hypotheses across knowledge layers, parse evidence frontmatter for freshness, and list decision records to compute phase and warnings.

How do I detect stale or expired evidence in an FPF workflow?

Detect stale or expired evidence by parsing the valid_until dates in evidence frontmatter fields, classifying each item as fresh, stale, or expired, and surfacing warnings for items needing review.

What is FPF phase detection and how does it work?

FPF phase detection infers the current workflow phase by counting files in each knowledge layer (L0, L1, L2) within the .fpf directory and applying the provided phase detection logic to the distribution.

Does the FPF status skill require specific directory structures?

Yes, it requires a .fpf directory containing subdirectories for knowledge layers L0, L1, L2, evidence, and decisions to verify the structure and compute knowledge base health metrics.

How do I audit decision records in an FPF knowledge base?

Audit decision records by listing DRRs within the .fpf decisions directory to summarize completed decisions, identify winners, and indicate recent workflow progress to maintainers.