fpf:reset
Reset the FPF reasoning cycle to start fresh
Best use case
fpf:reset is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Reset the FPF reasoning cycle to start fresh
Teams using fpf:reset should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/reset/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How fpf:reset Compares
| Feature / Agent | fpf:reset | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Reset the FPF reasoning cycle to start fresh
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Reset Cycle Reset the FPF reasoning cycle to start fresh. ## Action (Run-Time) ### Option 1: Soft Reset (Archive Current Session) Create a session archive and clear active work: 1. **Create Session Archive** Create a file in `.fpf/sessions/` to record the completed/abandoned session: ```markdown # In .fpf/sessions/session-2025-01-15-reset.md --- id: session-2025-01-15-reset action: reset created: 2025-01-15T16:00:00Z reason: user_requested --- # Session Archive: 2025-01-15 **Reset Reason**: User requested fresh start ## State at Reset ### Hypotheses - L0: 2 (proposed) - L1: 1 (verified) - L2: 0 (validated) - Invalid: 1 (rejected) ### Files Archived - .fpf/knowledge/L0/hypothesis-a.md - .fpf/knowledge/L0/hypothesis-b.md - .fpf/knowledge/L1/hypothesis-c.md ### Decision Status No decision was finalized. ## Notes Session ended without decision. Hypotheses preserved for potential future reference. ``` 2. **Move Active Work to Archive** (Optional) If user wants to clear the knowledge directories: ```bash mkdir -p .fpf/archive/session-2025-01-15 mv .fpf/knowledge/L0/*.md .fpf/archive/session-2025-01-15/ 2>/dev/null || true mv .fpf/knowledge/L1/*.md .fpf/archive/session-2025-01-15/ 2>/dev/null || true mv .fpf/knowledge/L2/*.md .fpf/archive/session-2025-01-15/ 2>/dev/null || true ``` 3. **Report to User** ```markdown ## Reset Complete Session archived to: .fpf/sessions/session-2025-01-15-reset.md Current state: - L0: 0 hypotheses - L1: 0 hypotheses - L2: 0 hypotheses Ready for new reasoning cycle. Run `/fpf:propose-hypotheses` to start. ``` ### Option 2: Hard Reset (Delete All) **WARNING**: This permanently deletes all FPF data. ```bash rm -rf .fpf/knowledge/L0/*.md rm -rf .fpf/knowledge/L1/*.md rm -rf .fpf/knowledge/L2/*.md rm -rf .fpf/knowledge/invalid/*.md rm -rf .fpf/evidence/*.md rm -rf .fpf/decisions/*.md ``` Only do this if explicitly requested by user. ### Option 3: Decision Reset (Keep Knowledge) If user wants to re-evaluate existing hypotheses: 1. Move L2 hypotheses back to L1 (re-audit) 2. Or move L1 hypotheses back to L0 (re-verify) ```bash # Re-audit: L2 -> L1 mv .fpf/knowledge/L2/*.md .fpf/knowledge/L1/ # Re-verify: L1 -> L0 mv .fpf/knowledge/L1/*.md .fpf/knowledge/L0/ ```
Related Skills
cost-optimization
Optimize cloud costs through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing c...
copilot-usage-metrics
Retrieve and display GitHub Copilot usage metrics for organizations and enterprises using the GitHub CLI and REST API.
copilot-sdk
Build agentic applications with GitHub Copilot SDK. Use when embedding AI agents in apps, creating custom tools, implementing streaming responses, managing sessions, connecting to MCP servers, or creating custom agents. Triggers on Copilot SDK, GitHub SDK, agentic app, embed Copilot, programmable agent, MCP server, custom agent.
copilot-instructions-blueprint-generator
Technology-agnostic blueprint generator for creating comprehensive copilot-instructions.md files that guide GitHub Copilot to produce code consistent with project standards, architecture patterns, and exact technology versions by analyzing existing codebase patterns and avoiding assumptions.
copilot-docs
Configure GitHub Copilot with custom instructions. Use when setting up .github/copilot-instructions.md, customizing Copilot behavior, or creating repository-specific AI guidance. Triggers on Copilot instructions, copilot-instructions.md, GitHub Copilot config.
conventional-commit
Prompt and workflow for generating conventional commit messages using a structured XML format. Guides users to create standardized, descriptive commit messages in line with the Conventional Commits specification, including instructions, examples, and validation.
contagious
Engineer word-of-mouth and virality using the STEPPS framework (Social Currency, Triggers, Emotion, Public, Practical Value, Stories). Use when the user mentions "go viral", "word of mouth", "shareable content", "social currency", or "why people share". Covers environmental triggers and high-arousal emotional content. For sticky messaging, see made-to-stick. For persuasion tactics, see influence-psychology.
constant-time-analysis
Detects timing side-channel vulnerabilities in cryptographic code. Use when implementing or reviewing crypto code, encountering division on secrets, secret-dependent branches, or constant-time programming questions in C, C++, Go, Rust, Swift, Java, Kotlin, C#, PHP, JavaScript, TypeScript, Python, or Ruby.
connect
Connect Claude to any app. Send emails, create issues, post messages, update databases - take real actions across Gmail, Slack, GitHub, Notion, and 1000+ services.
connect-apps
Connect Claude to external apps like Gmail, Slack, GitHub. Use this skill when the user wants to send emails, create issues, post messages, or take actions in external services.
conductor-revert
Git-aware undo by logical work unit (track, phase, or task)
git:compare-worktrees
Compare files and directories between git worktrees or worktree and current branch