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
- [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/:
- Read the
valid_untilfield 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
- Fresh:
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.
More from neolabhq/context-engineering-kit
sdd:plan
Refine, parallelize, and verify a draft task specification into a fully planned implementation-ready task
550sdd:implement
Implement a task with automated LLM-as-Judge verification for critical steps
525customaize-agent:prompt-engineering
Use this skill when you writing commands, hooks, skills for Agent, or prompts for sub agents or any other LLM interaction, including optimizing prompts, improving LLM outputs, or designing production prompt templates.
512code-review:review-local-changes
Comprehensive review of local uncommitted changes using specialized agents with code improvement suggestions
511sdd:brainstorm
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
509sdd:add-task
creates draft task file in .specs/tasks/draft/ with original user intent
503