# Plan

> Entry point for planning work — routes to the skills that own the substance. Use when the user asks to plan, sequence, or scope something and it is not yet clear which kind of planning is needed.

- Skill: `bfollington/plan` (Agent Skill)
- Install (CLI): `npx skillmds@latest add bfollington/plan`
- Raw SKILL.md: https://api.skillmd.com/api/skills/bfollington/plan/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: bfollington (https://skillmd.com/u/bfollington)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/bfollington/plan

---


# Plan

No implementation yet. Consider the path ahead.

Planning is three separable questions, each owned by its own skill. Load what the moment calls for rather than all of them:

- **Is this worth building, and what is the smallest thing that would tell us?** → `idea-to-prototype`
- **What is the sequence, and how do we know each step landed?** → `convergent-planning`
- **What can happen at once, and what has to be settled first?** → `concurrent-change`

Most planning that arrives as "plan this feature" is the second. Where the change touches concepts the system already commits to, `surface-forks` comes first — the collisions determine the plan.

The through-line: a plan is a sequence of ambiguity collapses, and a step nothing could contradict is not a step.