Productivity

fpf:status

neolabhq/context-engineering-kit · updated Apr 8, 2026

$npx skills add https://github.com/neolabhq/context-engineering-kit --skill fpf:status
summary

Display the current state of the FPF knowledge base.

skill.md

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

## 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 Phase
Based 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:

Condition Phase Next Step
No .fpf/ directory NOT INITIALIZED Run /fpf:propose-hypotheses
L0 > 0, L1 = 0, L2 = 0 ABDUCTION Continue with verification
L1 > 0, L2 = 0 DEDUCTION Continue with validation
L2 > 0, no recent DRR INDUCTION Continue with audit and decision
Recent DRR exists DECISION COMPLETE Review decision
All empty IDLE Run /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.
general reviews

Ratings

4.510 reviews
  • Shikha Mishra· Oct 10, 2024

    fpf:status is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Piyush G· Sep 9, 2024

    Keeps context tight: fpf:status is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Chaitanya Patil· Aug 8, 2024

    Registry listing for fpf:status matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Sakshi Patil· Jul 7, 2024

    fpf:status reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Ganesh Mohane· Jun 6, 2024

    I recommend fpf:status for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Oshnikdeep· May 5, 2024

    Useful defaults in fpf:status — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Dhruvi Jain· Apr 4, 2024

    fpf:status has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Rahul Santra· Mar 3, 2024

    Solid pick for teams standardizing on skills: fpf:status is focused, and the summary matches what you get after install.

  • Pratham Ware· Feb 2, 2024

    We added fpf:status from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Yash Thakker· Jan 1, 2024

    fpf:status fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.