How to install status
npx skills add https://github.com/neolabhq/context-engineering-kit --skill statusFull instructions (SKILL.md)
Source of truth, from neolabhq/context-engineering-kit.
name: status description: "Display the current state of the FPF knowledge base"
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.
Related skills
More from neolabhq/context-engineering-kit and the wider catalog.

subagent-driven-development
Use when executing implementation plans with independent tasks in the current session or facing 3+ independent issues that can be investigated without shared state or dependencies - dispatches fresh subagent for each task with code review between tasks, enabling fast iteration with quality gates

test-driven-development
Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first

test-prompt
Use when creating or editing any prompt (commands, hooks, skills, subagent instructions) to verify it produces desired behavior - applies RED-GREEN-REFACTOR cycle to prompt engineering using subagents for isolated testing

test-skill
Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholes

thought-based-reasoning
Use when tackling complex reasoning tasks requiring step-by-step logic, multi-step arithmetic, commonsense reasoning, symbolic manipulation, or problems where simple prompting fails - provides comprehensive guide to Chain-of-Thought and related prompting techniques (Zero-shot CoT, Self-Consistency, Tree of Thoughts, Least-to-Most, ReAct, PAL, Reflexion) with templates, decision matrices, and research-backed patterns

tree-of-thoughts
Execute tasks through systematic exploration, pruning, and expansion using Tree of Thoughts methodology with meta-judge evaluation specifications and multi-agent evaluation