fpf:reset

Reset the FPF reasoning cycle to start fresh

771 stars

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

$curl -o ~/.claude/skills/reset/SKILL.md --create-dirs "https://raw.githubusercontent.com/NeoLabHQ/context-engineering-kit/main/plugins/fpf/skills/reset/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/reset/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How fpf:reset Compares

Feature / Agentfpf:resetStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/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

tech-stack:add-typescript-best-practices

771
from NeoLabHQ/context-engineering-kit

Setup TypeScript best practices and code style rules in CLAUDE.md

tdd:write-tests

771
from NeoLabHQ/context-engineering-kit

Systematically add test coverage for all local code changes using specialized review and development agents. Add tests for uncommitted changes (including untracked files), or if everything is commited, then will cover latest commit.

tdd:test-driven-development

771
from NeoLabHQ/context-engineering-kit

Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first

tdd:fix-tests

771
from NeoLabHQ/context-engineering-kit

Systematically fix all failing tests after business logic changes or refactoring

sdd:plan

771
from NeoLabHQ/context-engineering-kit

Refine, parallelize, and verify a draft task specification into a fully planned implementation-ready task

sdd:implement

771
from NeoLabHQ/context-engineering-kit

Implement a task with automated LLM-as-Judge verification for critical steps

sdd:create-ideas

771
from NeoLabHQ/context-engineering-kit

Generate ideas in one shot using creative sampling

sdd:brainstorm

771
from NeoLabHQ/context-engineering-kit

Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes

sdd:add-task

771
from NeoLabHQ/context-engineering-kit

creates draft task file in .specs/tasks/draft/ with original user intent

sadd:tree-of-thoughts

771
from NeoLabHQ/context-engineering-kit

Execute tasks through systematic exploration, pruning, and expansion using Tree of Thoughts methodology with meta-judge evaluation specifications and multi-agent evaluation

sadd:subagent-driven-development

771
from NeoLabHQ/context-engineering-kit

Use when executing implementation plans with independent tasks in the current session or facing 3+ independent issues that can be investigated without shared state or dependencies - dispatches fresh subagent for each task with code review between tasks, enabling fast iteration with quality gates

sadd:multi-agent-patterns

771
from NeoLabHQ/context-engineering-kit

Design multi-agent architectures for complex tasks. Use when single-agent context limits are exceeded, when tasks decompose naturally into subtasks, or when specializing agents improves quality.