fpf:status

Display the current state of the FPF knowledge base.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "fpf:status" with this command: npx skills add neolabhq/context-engineering-kit/neolabhq-context-engineering-kit-fpf-status

Status Check

Display the current state of the FPF knowledge base.

Action (Run-Time)

  • Check Directory Structure: Verify .fpf/ exists and contains required subdirectories.

  • Count Hypotheses: List files in each knowledge layer:

  • .fpf/knowledge/L0/ (Proposed)

  • .fpf/knowledge/L1/ (Verified)

  • .fpf/knowledge/L2/ (Validated)

  • .fpf/knowledge/invalid/ (Rejected)

  • Check Evidence Freshness: Scan .fpf/evidence/ for expired evidence.

  • Count Decisions: List files in .fpf/decisions/ .

  • Report to user.

Status Report Format

FPF Status

Directory Structure

  • .fpf/ exists
  • knowledge/L0/ exists
  • knowledge/L1/ exists
  • knowledge/L2/ exists
  • evidence/ exists
  • decisions/ exists

Current Phase

Based on hypothesis distribution: ABDUCTION | DEDUCTION | INDUCTION | DECISION | IDLE

Hypothesis Counts

LayerCountStatus
L0 (Proposed)3Awaiting verification
L1 (Verified)2Awaiting validation
L2 (Validated)1Ready for decision
Invalid1Rejected

Evidence Status

TotalFreshStaleExpired
5311

Warnings

  • 1 evidence file is EXPIRED: ev-benchmark-old-2024-06-15
  • Consider running /fpf:decay to review stale evidence

Recent Decisions

DRRDateWinner
DRR-2025-01-15-use-redis2025-01-15redis-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/ :

  • Read the valid_until field from frontmatter

  • Compare with current date

  • 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

LayerCount
L03
L10
L20
Invalid0

Evidence Status

No evidence files yet (hypotheses not validated).

No Warnings

All systems nominal.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

ddd:software-architecture

No summary provided by upstream source.

Repository SourceNeeds Review
Automation

customaize-agent:prompt-engineering

No summary provided by upstream source.

Repository SourceNeeds Review
General

sdd:plan

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

code-review:review-local-changes

No summary provided by upstream source.

Repository SourceNeeds Review