메뉴
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>/.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
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.
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.
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>/.
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.
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.
| 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"] |
Turn an ambiguous request into a bounded plan that can be executed by Claude
and Codex under the same pi runtime.
plans/<feature>/plan.md.plans/<feature>/options.md.plans/<feature>/decisions.md.plans/<feature>/sprint-contract.md before handing work to
a builder.plans/<feature>/context.mdplans/<feature>/options.mdplans/<feature>/plan.mdplans/<feature>/decisions.mdplans/<feature>/sprint-contract.md