// 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".
| name | fpf-active |
| description | 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". |
This skill manages the FPF global on/off switch. FPF can be enabled or disabled globally across all Claude Code sessions. When disabled, skills are physically archived, hooks stop running, and CLAUDE.md is moved out — FPF becomes invisible until re-enabled.
This skill itself is never toggled. It lives at ~/.claude/skills/fpf-active/ permanently
and remains available whether FPF is enabled or disabled.
Invoke with one of:
/fpf-active — show status/fpf-active status — show status/fpf-active enable — enable FPF globally/fpf-active disable — disable FPF globallyUse the Read tool to read these files (they may not exist yet):
~/.fpf/global-state — contains ENABLED or DISABLED~/.fpf/config.json — contains scope, level0 flag, registered projectsReport:
~/.fpf/config.json~/.fpf/fpf-toggle.shRun the toggle script using the Bash tool:
bash ~/.fpf/fpf-toggle.sh [enable|disable]
The script handles all file moves (skills, hooks, settings.json, CLAUDE.md) and tweakcc restore/apply.
Always remind the user:
Restart your Claude Code session for the change to take effect. Skills and hooks are only loaded at session start.
If the toggle script is not found:
~/.fpf/fpf-toggle.shnot found. FPF may not be installed or was installed without the toggle infrastructure. Re-run the installer to fix this.
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.
Show current FPF session state — tier, edit count, artifacts, pending gates. Read-only diagnostic.