FPF 知识库状态检查工具：监控假设、证据与决策生命周期

fpf%3Astatus by neolabhq/context-engineering-kit

253 周安装量

765 GitHub Stars

GitHub

安装命令

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

软件工程监控知识管理

🇨🇳中文介绍

状态检查

显示 FPF 知识库的当前状态。

操作（运行时）

检查目录结构： 验证 .fpf/ 目录是否存在并包含所需的子目录。
统计假设： 列出各知识层中的文件： * .fpf/knowledge/L0/ （已提出） * .fpf/knowledge/L1/ （已验证） * .fpf/knowledge/L2/ （已确认） * .fpf/knowledge/invalid/ （已拒绝）
检查证据新鲜度： 扫描 .fpf/evidence/ 目录中过期的证据。
统计决策： 列出 .fpf/decisions/ 目录中的文件。
向用户报告。

状态报告格式

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

相关 Skills

前端性能优化指南：识别瓶颈与优化策略，提升LCP、FID、CLS核心指标

47,000 周安装

前端代码审计工具 - 自动化检测可访问性、性能、响应式设计、主题化与反模式

46,200 周安装

网站审计工具 - 使用 squirrelscan CLI 全面检测 SEO、性能、安全及技术问题

43,300 周安装

Lark CLI Wiki API 使用指南：获取知识空间节点信息与权限管理

35,300 周安装

## FPF 状态

### 目录结构
- [x] .fpf/ 存在
- [x] knowledge/L0/ 存在
- [x] knowledge/L1/ 存在
- [x] knowledge/L2/ 存在
- [x] evidence/ 存在
- [x] decisions/ 存在

### 当前阶段
基于假设分布：ABDUCTION | DEDUCTION | INDUCTION | DECISION | IDLE

### 假设数量统计

| 层级 | 数量 | 状态 |
|-------|-------|--------|
| L0 (已提出) | 3 | 等待验证 |
| L1 (已验证) | 2 | 等待确认 |
| L2 (已确认) | 1 | 准备决策 |
| 无效 | 1 | 已拒绝 |

### 证据状态

| 总计 | 新鲜 | 陈旧 | 过期 |
|-------|-------|-------|---------|
| 5 | 3 | 1 | 1 |

### 警告

- 1 个证据文件已过期：ev-benchmark-old-2024-06-15
- 考虑运行 `/fpf:decay` 来审查陈旧证据

### 近期决策

| DRR | 日期 | 胜出方案 |
|-----|------|--------|
| DRR-2025-01-15-use-redis | 2025-01-15 | redis-caching |

条件	阶段	下一步行动
无 `.fpf/` 目录	未初始化	运行 `/fpf:propose-hypotheses`
L0 > 0, L1 = 0, L2 = 0	ABDUCTION	继续验证
L1 > 0, L2 = 0	DEDUCTION	继续确认
L2 > 0, 无近期 DRR	INDUCTION	继续审计和决策
存在近期 DRR	决策完成	审查决策
全部为空	IDLE	运行 `/fpf:propose-hypotheses`

从前置元数据中读取 valid_until 字段
与当前日期比较
分类： * 新鲜：valid_until > 今天 + 30 天 * 陈旧：valid_until > 今天但 < 今天 + 30 天 * 过期：valid_until < 今天

🇺🇸English

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_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

| Layer | Count |
|-------|-------|
| L0 | 3 |
| L1 | 0 |
| L2 | 0 |
| Invalid | 0 |

### Evidence Status

No evidence files yet (hypotheses not validated).

### No Warnings

All systems nominal.

Weekly Installs

151

Repository

neolabhq/contex…ring-kit

GitHub Stars

699

First Seen

Feb 19, 2026

Installed on

opencode146

codex145

github-copilot144

gemini-cli143

kimi-cli141

cursor141