Fp Optimize Path
Use only when routed by FP after MVP scope is defined to choose the first safe reuse rung and compile the final Execution Brief.
Fp Semantic Architecture
Use only when routed by FP after delete-scope and only when the scoped MVP crosses modules or has real coupling risk.
Review Changes
Perform a structured code review using change detection and impact
Fp Question Requirements
Use only when routed by FP for vague, risky, large, product-facing, or assumption-heavy work; separates facts, decisions, failure paths, success criteria, and non-goals.
Fp Shorten Iteration
Use only when routed by FP because work is too large, an attempt failed, or the selected path needs evidence-backed micro-loops.
Fp Debug
Debug-first diagnosis protocol for unknown failures. Use when the cause is unknown, a bug needs diagnosis before fixing, or the user asks 'what's wrong' without requesting a fix. Provides structured hypothesis-probe-decision loop with evidence tracking.
Fp Adaptive Improvement
Use only when routed by FP after a non-trivial evidenced run to stage a reusable checklist, schema, or automation candidate.
Explore Codebase
Navigate and understand codebase structure using the knowledge graph
Fp Codebase
Codebase analysis and impact mapping. Use when reviewing, modifying, or understanding user code where the blast radius spans multiple files. Provides code-review-graph MCP integration and grep-fallback protocols for computing change impact.
Fp Delete Scope
Use only when routed by FP after requirements work to apply the seven-rung reuse ladder, delete scope, and define the smallest verifiable MVP.
Fp Delegated Execution
Use only when routed by FP after an executable plan is accepted and the current host exposes a verified subagent runtime; dispatch a fresh implementer, task reviewer, bounded fixer/re-review loop, final integration reviewer, and parent verification.
Fp Provider Compatibility
Use only when routed by FP for an agent host using a non-native model provider, API-compatible endpoint, gateway, or local proxy, or when loops, retries, token spend, cache accounting, streaming, tool calls, or encoding are suspect.
Fp
Use automatically when the user's goal is engineering work (build, change, diagnose, review, test, operate, or plan software, repositories, infrastructure, or agent tooling), or when explicitly invoked with \"FP:\" or \"$fp\". Do not use for casual conversation or other non-engineering goals.
Fp Continue
Cross-session task continuation and handoff. Use when resuming incomplete work from a previous session, after context compaction, or when a task spans multiple sessions. Provides structured handoff fingerprints and resume protocols.
Fp Dispatch Parallel Domains
Use only when routed by FP for two or more explicitly independent problem domains whose dependencies, writer paths, generated outputs, state, and verification can be isolated before bounded fan-out and parent fan-in.
Debug Issue
Systematically debug issues using graph-powered code navigation
Fp Metrics
Use only when routed by FP after a canonical Evidence Ledger and when measurement or a comparable baseline matters.
Generalization Gate
Evaluate evidence-backed checklist, schema, skill-patch, or automation candidates before shadowing or promotion. Use after adaptive improvement, for background-learning proposals, or whenever a rule inferred from a small number of runs could overfit, underfit, leak its holdout cases, or cause negative transfer.
Refactor Safely
Plan and execute safe refactoring using dependency analysis
Fp Evidence Ledger
Use only when routed by FP after execution, failure, or handoff to record canonical claims, checks, scope, authority, experiments, and optional continuation evidence.
Fp Schema Memory
Use only when routed by FP after repeated evidence has accumulated; store reusable patterns and stop conditions, never raw context.
Fp Self Evolve
FP self-evolution: auto-capture lessons from tasks, nudge reflection every ~10 turns, update MEMORY.md and USER.md across projects. Use when any task completes or after a significant error, correction, or complex workflow (5+ tool calls).
Fp Live System
Remote, stateful, or embedded system operations. Use when working with routers, OpenWrt, embedded Linux, VMs, containers, remote servers, or any target where a restart or 'ready' label is not proof of function. Provides management path preservation and verification protocols.