Status

NeoLabHQ/context-engineering-kit/plugins/fpf/skills/status

by NeoLabHQ23e2428e809d77717f8acc9659c374a3a1fcb93eNo licenseListed Oct 9, 2026Updated Oct 9, 2026

Display the current state of the FPF knowledge base

Instructions onlyProductivity & Workflow
AI-generated overview

Displays the current state of an FPF knowledge base, counting hypotheses, evidence and decisions.

What it does
Inspects the .fpf/ directory structure and reports whether the required subdirectories exist. It counts hypothesis files per knowledge layer (L0, L1, L2, invalid), checks evidence freshness against valid_until dates, and counts decision files. It then prints a status report with a detected workflow phase, counts, evidence status, warnings and recent decisions.
When to use it
Use when you want an overview of an FPF knowledge base's current state or workflow phase. It is also useful before deciding the next step, such as verification, validation, audit or decay review.
Requirements
No scripts; instructions only. It reads a local .fpf/ directory containing knowledge, evidence and decisions subdirectories, and needs the current date to classify evidence freshness.

Status Check

Display the current state of the FPF knowledge base.

Action (Run-Time)

  1. Check Directory Structure: Verify .fpf/ exists and contains required subdirectories.
  2. Count Hypotheses: List files in each knowledge layer:
    • .fpf/knowledge/L0/ (Proposed)
    • .fpf/knowledge/L1/ (Verified)
    • .fpf/knowledge/L2/ (Validated)
    • .fpf/knowledge/invalid/ (Rejected)
  3. Check Evidence Freshness: Scan .fpf/evidence/ for expired evidence.
  4. Count Decisions: List files in .fpf/decisions/.
  5. Report to user.

Status Report Format

markdown
## FPF Status
### Directory Structure- [x] .fpf/ exists- [x] knowledge/L0/ exists- [x] knowledge/L1/ exists- [x] knowledge/L2/ exists- [x] evidence/ exists- [x] decisions/ exists
### Current PhaseBased on hypothesis distribution: ABDUCTION | DEDUCTION | INDUCTION | DECISION | IDLE
### Hypothesis Counts
| Layer | Count | Status ||-------|-------|--------|| L0 (Proposed) | 3 | Awaiting verification || L1 (Verified) | 2 | Awaiting validation || L2 (Validated) | 1 | Ready for decision || Invalid | 1 | Rejected |
### Evidence Status
| Total | Fresh | Stale | Expired ||-------|-------|-------|---------|| 5 | 3 | 1 | 1 |
### Warnings
- 1 evidence file is EXPIRED: ev-benchmark-old-2024-06-15- Consider running `/fpf:decay` to review stale evidence
### Recent Decisions
| DRR | Date | Winner ||-----|------|--------|| DRR-2025-01-15-use-redis | 2025-01-15 | redis-caching |

Phase Detection Logic

Determine current phase by examining the knowledge base state:

ConditionPhaseNext Step
No .fpf/ directoryNOT INITIALIZEDRun /fpf:propose-hypotheses
L0 > 0, L1 = 0, L2 = 0ABDUCTIONContinue with verification
L1 > 0, L2 = 0DEDUCTIONContinue with validation
L2 > 0, no recent DRRINDUCTIONContinue with audit and decision
Recent DRR existsDECISION COMPLETEReview decision
All emptyIDLERun /fpf:propose-hypotheses

Evidence Freshness Check

For each evidence file in .fpf/evidence/:

  1. Read the valid_until field from frontmatter
  2. Compare with current date
  3. Classify:
    • Fresh: valid_until > today + 30 days
    • Stale: valid_until > today but < today + 30 days
    • Expired: valid_until < today

If any evidence is stale or expired, warn the user and suggest /fpf:decay.

Example Output

## FPF Status
### Current Phase: DEDUCTION
You have 3 hypotheses in L0 awaiting verification.Next step: Continue the FPF workflow to process L0 hypotheses.
### Hypothesis Counts
| Layer | Count ||-------|-------|| L0 | 3 || L1 | 0 || L2 | 0 || Invalid | 0 |
### Evidence Status
No evidence files yet (hypotheses not validated).
### No Warnings
All systems nominal.

Source and attribution

Source:NeoLabHQ/context-engineering-kitinplugins/fpf/skills/statusat commit23e2428

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal