| name | fpf-skill |
| version | 0.1.0 |
| description | Practical FPF usage guide for the vfpf harness. Use when a task needs a fit
check, an FPF entry route, starter artifacts, mixed-team handoff rules, or
an FPF-shaped review rubric without loading the full specification into the
prompt.
|
| allowed-tools | ["Read"] |
fpf-skill
Goal
Use FPF as a route menu and coordination scaffold for this harness, not as a
theory dump.
Load order
- Start with
references/00-fit-check.md to decide whether FPF is warranted.
- Then load
references/01-five-entry-routes.md and pick one route.
- For AI-assisted use, load
references/02-ai-assistant-mode.md.
- For expected outputs, load
references/03-starter-artifacts.md.
- For orchestration, load
references/04-mixed-team-loop.md.
- For critique, load
references/05-fpf-review-rubric.md.
- Treat
references/FPF-spec.md as the canonical pointer to the upstream FPF
repository.
Rules
- Use plain engineer-manager language first.
- Introduce internal FPF names only when they add precision.
- Default outputs are artifacts, not essays.
- Prefer bounded contexts, criteria, alternatives, handoffs, and evidence gaps
over abstract explanation.
- Do not paste or vendor the full FPF spec into working prompts.
Exit criteria
- The chosen route is explicit.
- The task leaves behind concrete artifacts or review findings.
- Any deeper FPF reading is justified by the task, not by curiosity.
