Run any Skill in Manus with one click

vfpf-plan

Stars0

Forks0

UpdatedApril 1, 2026 at 19:07

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>/.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

venikman

venikman/gstack

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

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.md
plans/<feature>/options.md
plans/<feature>/plan.md
plans/<feature>/decisions.md
plans/<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.

More from this repository

same repository

vfpf-build

venikman/gstack

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.

2026-04-020

effect-best-practices

venikman/gstack

Local Effect doctrine for the pi healthcare harness. Use when a task touches files importing effect and needs consistent rules for services, schemas, errors, layers, config, and structured effectful composition.

2026-04-010

fpf-skill

venikman/gstack

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.

2026-04-010

vfpf-eval

venikman/gstack

Portable evaluation skill for pi. Use when comparing runs, agent mixes, or orchestration changes for Claude and Codex. Only compare results inside an explicit comparability frame and tie outputs back to plans/<feature>/.

2026-04-010

vfpf-orchestrate

venikman/gstack

Portable orchestration skill for pi. Use when Claude and Codex should work as peer agents with bounded scopes, stable task cards, and evidence-backed handoffs. Use it to drive the orchestrator -> builder -> reviewer loop and keep all delegated work tied to plans/<feature>/ artifacts.

2026-04-010

vfpf-review

venikman/gstack

Portable review skill for pi. Use when work needs a findings-first review that checks behavior, regression risk, evidence quality, and plan adherence across Claude and Codex outputs. Review against plans/<feature>/ artifacts and act as the blocking reviewer in the orchestrator loop.

2026-04-010

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.md
plans/<feature>/options.md
plans/<feature>/plan.md
plans/<feature>/decisions.md
plans/<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.