| name | vfpf-plan |
| version | 0.1.0 |
| description | Portable planning skill for pi. Use when a feature needs bounded context,
explicit alternatives, and one approved execution plan before implementation.
Keep the output artifact-first so Claude and Codex can work against the same
plan surface. Write plans under plans/<feature>/.
|
| allowed-tools | ["Read","Write","Edit"] |
vfpf-plan
Goal
Turn an ambiguous request into a bounded plan that can be executed by Claude
and Codex under the same pi runtime.
Rules
- Start with bounded context, not implementation.
- Separate role, method, and work.
- Generate 2-4 viable options before selecting one.
- Record the selected approach in
plans/<feature>/plan.md.
- Record rejected alternatives and why in
plans/<feature>/options.md.
- Capture non-obvious tradeoffs in
plans/<feature>/decisions.md.
- Prepare the first
plans/<feature>/sprint-contract.md before handing work to
a builder.
Required artifacts
plans/<feature>/context.mdplans/<feature>/options.mdplans/<feature>/plan.mdplans/<feature>/decisions.mdplans/<feature>/sprint-contract.md
Exit criteria
- Scope is explicit.
- Acceptance criteria are explicit.
- Risks and open questions are named.
- The plan is specific enough for delegation without reinterpretation.
