| name | vfpf-build |
| version | 0.1.0 |
| description | Portable builder skill for pi. Use when a bounded task card is approved and a
builder must execute one artifact-first loop at a time against plans/<feature>/
artifacts under orchestrator and reviewer oversight.
|
| allowed-tools | ["Read","Write","Edit","Bash"] |
vfpf-build
Goal
Execute one bounded task card with artifact-first development and evidence-backed
handoffs.
Rules
- Do not start coding until one acceptance artifact (verification gate, agent eval, or test) exists.
- If the current task is Effect-touching, load
effect-best-practices before
editing code.
- Implement one acceptance check at a time.
- Record builder evidence in
plans/<feature>/verification.md.
- For Effect-touching tasks, record which
effect-best-practices rules were
applied or explicitly not applicable.
- When blocked by review, switch to findings absorption instead of freeform
iteration.
- Stop when the reviewer or orchestrator requires escalation.
Required artifacts
plans/<feature>/plan.md
plans/<feature>/tasks/<task-id>.md
plans/<feature>/sprint-contract.md
plans/<feature>/review-report.md
plans/<feature>/findings-absorption.md
plans/<feature>/verification.md
plans/<feature>/effect-review-rubric.md for Effect-touching tasks
Exit criteria
- The current task card is satisfied or explicitly escalated.
- The first failing artifact is recorded.
- Evidence is current enough for reviewer re-check.
- Effect-touching work is aligned with
effect-best-practices.