Reset the FPF reasoning cycle to start fresh
49
36%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/fpf/skills/reset/SKILL.mdReset the FPF reasoning cycle to start fresh.
Create a session archive and clear active work:
Create a file in .fpf/sessions/ to record the completed/abandoned session:
# 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.If user wants to clear the knowledge directories:
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## 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.WARNING: This permanently deletes all FPF data.
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/*.mdOnly do this if explicitly requested by user.
If user wants to re-evaluate existing hypotheses:
# Re-audit: L2 -> L1
mv .fpf/knowledge/L2/*.md .fpf/knowledge/L1/
# Re-verify: L1 -> L0
mv .fpf/knowledge/L1/*.md .fpf/knowledge/L0/dedca19
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.