// Show current FPF session state — tier, edit count, artifacts, pending gates. Read-only diagnostic.
| name | fpf-status |
| description | Show current FPF session state — tier, edit count, artifacts, pending gates. Read-only diagnostic. |
A read-only diagnostic that shows the current FPF session state at a glance. No artifacts created, no side effects. Use when you want to know "where am I in the FPF process?"
Read and report the following (use Read/Glob only):
Session state:
.fpf/.session-active — exists? fresh?.fpf/.session-tier — current tier (T1/T2/T3/T4).fpf/.trivial-session — trivial bypass active?.fpf/.source-edit-count — current edit count.fpf/.review-done — review completed?Artifacts this session (match session ID prefix):
.fpf/anomalies/.fpf/characterizations/.fpf/characterizations/.fpf/decisions/.fpf/portfolios/.fpf/evidence/.fpf/worklog/Pending gates (what hooks will check next):
Config (from .fpf/config.sh):
Report as a concise table to the user. Example:
FPF Status — Session e00ed34f
Tier: T3 | Edits: 12 | Trivial: no
Artifacts:
PROB-e00ed34f--feature.md ✓ (3 hypotheses)
CHR: none (inline in PROB)
SPORT-e00ed34f--feature.md ✓ (3 variants)
SEL: none ← next step
EVID: none ← needed before end
Pending: /fpf-selection → implement → /fpf-evidence → /fpf-review
FPF global toggle and status. Check whether FPF is enabled or disabled globally. Enable or disable FPF across all Claude Code sessions. Triggers on "fpf status", "fpf on", "fpf off", "enable fpf", "disable fpf", "is fpf active", "/fpf-active".
FPF session bootstrap. MUST be auto-invoked at the start of any non-trivial task. Writes sentinel, triggers worklog, activates FPF rules. After this, MUST invoke /fpf-worklog.
Think through a problem by working through the problem card template. Design what problem you're solving and how you'll know it's solved. MUST invoke for debugging, new features, design decisions, or any substantive work.
End-of-session quality gate. Verify the creative and assurance pipeline — not just artifacts. MUST invoke before ending any non-trivial session.
Perform qualitative Pareto analysis on variants, apply explicit selection policy, record stepping-stone bets. Think through the trade-offs using the selection template.
Explore the solution space by generating ≥3 genuinely distinct variants within the chosen method family. Think through alternatives using the portfolio template as scaffolding.
