pibun: Skill for Claude Code

Phased Plan

Create a phased build plan from a project specification. This skill establishes a file system convention for managing multi-session builds with shared memory and context continuity.

When to Use

• A project spec exists but needs to be broken into buildable phases
• Work will span multiple sessions and needs context continuity
• You need to prevent context rot across sessions

Process

1. Read the Spec

Read the project specification file (usually SPEC.md, docs/, or similar) and understand the full scope.

Also read existing project context if present:

• CLAUDE.md — project identity and conventions
• .pi/AGENTS.md — agent capabilities and playbooks
• .agents/CONVENTIONS.md — build rules and patterns

2. Decompose into Phases

Break the spec into 3-8 phases following these rules:

• Each phase is self-contained and testable — it delivers working functionality
• Each phase builds on the previous — no forward dependencies
• Each phase is completable in 1-3 sessions — if too large, split further
• Each phase has clear exit criteria — how do you know it's done?
• Order by dependency first, then value

Sub-phases (e.g., 1A, 1B, 1C) are useful when a major phase has distinct sub-deliverables that should be reviewed independently. Use when:

• A phase has 15+ items that naturally group into 2-3 sub-deliverables
• You want autopilot to pause between sub-deliverables for review
• Different sub-phases need different expertise or context

3. Create .plan/ Directory

Create the following files:

.plan/PLAN.md — Master Plan

# {Project Name} — Build Plan

> **Spec:** {path to spec or description}
> **Status:** Not Started
> **Current Phase:** —
> **Last Session:** —

---

## Session Protocol

### At the START of every session:
1. Read `.plan/PLAN.md` (this file) — know where we are
2. Read `.plan/MEMORY.md` — absorb shared context and decisions
3. Read `.plan/DRIFT.md` — check for spec changes
4. Read `.agents/CONVENTIONS.md` — build patterns (if exists)
5. Identify the next uncompleted phase/item
6. State what you will do this session before starting

### At the END of every session:
1. Update item checkboxes in this file
2. Update `MEMORY.md` with anything the next session needs to know
3. Update `DRIFT.md` if any spec changes occurred
4. Log the session in `SESSION-LOG.md`
5. Write a **Handoff** note at the bottom of the session log entry
6. Run the build gate command (when applicable)

---

## Phase N — {Name}

**Goal:** {One sentence describing what this phase delivers}

- [ ] N.1 — {Item description}
- [ ] N.2 — {Item description}
- ...

**Exit criteria:** {How you know this phase is done}

---

## Parking Lot

Items discussed but deferred.

- [ ] {Future item}