How do I install the Wf Plan skill?

Run npx skillmds@latest add marchatton/wf-plan in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Wf Plan safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Wf Plan?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Wf Plan free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Wf Plan?

marchatton (@marchatton) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Wf Plan by marchatton — Agent Skill

Name: Wf Plan
Rating: 4.2 (5 reviews)
Author: marchatton

Wf Plan

This skill should only be used when the user uses the word workflow and asks to create a commit-ready, deep project plan from a shaped packet (brief, breadboard, risks, spikes) before development starts, with handoff/pickup boundaries to avoid context rot.

marchatton Updated Sep 22, 2026

File contents

wf-plan

Purpose

Turn a shaped packet (wf-shape dossier) into a commit-ready plan without re-litigating the shape.

Never implement production code. Only research and write the plan.

Inputs

Dossier folder path containing:

brief.md
breadboard-pack.md
risk-register.md
spike-investigation.md (if present)

Outputs

Inside the same dossier:

plan.md

Steps

Pickup (recommended if new thread)

Invoke pickup if repo/branch state is not fresh.

Ingest shaped packet (no idea refinement loop)

Read brief → breadboard → risk register → spikes.
If perimeter or top risks are missing: route back to wf-shape.

Create plan skeleton

Create plan.md with:
- scope (in/out)
- key flows + key logic
- acceptance criteria + verification plan
- sequencing/phases + stop points
- rollout/rollback + observability
- dependencies + risks

Local research (always)

Find similar patterns in repo.
Pull institutional learnings (docs/solutions, docs/LEARNINGS.md).
Record concrete file paths.

External research (conditional)

Always external for: security/auth, payments, privacy, external APIs, migrations.
Otherwise only if local context is thin.

Spec hardening (gap pass)

Edge cases, failure modes, concurrency, performance, data integrity, security threats.
Update acceptance criteria + verification.

Plan review passes

Simplicity, risk, ops/release, data integrity, security/privacy, UX/product.
Final mandatory pass: invoke oracle on the whole plan and integrate findings (or mark out-of-bounds).

Commit gate

GO only if:
- AC measurable
- verification per AC
- sequencing explicit
- rollout/rollback explicit
- no P1 unknowns remain

Handoff to build (recommended boundary)

Invoke handoff and include:
- plan path + summary of phases
- how to verify
- rollout notes
- biggest remaining risks
Recommend build in a fresh thread:
- /new then pickup then run wf-develop or wf-ralph

Verification

plan includes acceptance criteria + verification + rollout/rollback
oracle pass integrated

Go/No-Go

GO if the plan can be built without re-discovering the shape.
NO-GO if it depends on “we’ll figure it out during implementation”.

---name: wf-plandescription: This skill should only be used when the user uses the word workflow and asks to create a commit-ready, deep project plan from a shaped packet (brief, breadboard, risks, spikes) before development starts, with handoff/pickup boundaries to avoid context rot.---# wf-plan## PurposeTurn a shaped packet (wf-shape dossier) into a commit-ready plan without re-litigating the shape.Never implement production code. Only research and write the plan.## InputsDossier folder path containing:- `brief.md`- `breadboard-pack.md`- `risk-register.md`- `spike-investigation.md` (if present)## OutputsInside the same dossier:- `plan.md`## Steps0) Pickup (recommended if new thread)- Invoke `pickup` if repo/branch state is not fresh.1) Ingest shaped packet (no idea refinement loop)- Read brief → breadboard → risk register → spikes.- If perimeter or top risks are missing: route back to wf-shape.2) Create plan skeleton- Create `plan.md` with: - scope (in/out) - key flows + key logic - acceptance criteria + verification plan - sequencing/phases + stop points - rollout/rollback + observability - dependencies + risks3) Local research (always)- Find similar patterns in repo.- Pull institutional learnings (docs/solutions, docs/LEARNINGS.md).- Record concrete file paths.4) External research (conditional)- Always external for: security/auth, payments, privacy, external APIs, migrations.- Otherwise only if local context is thin.5) Spec hardening (gap pass)- Edge cases, failure modes, concurrency, performance, data integrity, security threats.- Update acceptance criteria + verification.6) Plan review passes- Simplicity, risk, ops/release, data integrity, security/privacy, UX/product.- Final mandatory pass: invoke `oracle` on the whole plan and integrate findings (or mark out-of-bounds).7) Commit gate- GO only if: - AC measurable - verification per AC - sequencing explicit - rollout/rollback explicit - no P1 unknowns remain8) Handoff to build (recommended boundary)- Invoke `handoff` and include: - plan path + summary of phases - how to verify - rollout notes - biggest remaining risks- Recommend build in a fresh thread: - `/new` then `pickup` then run wf-develop or wf-ralph## Verification- plan includes acceptance criteria + verification + rollout/rollback- oracle pass integrated## Go/No-Go- GO if the plan can be built without re-discovering the shape.- NO-GO if it depends on “we’ll figure it out during implementation”.

Frequently asked questions