pocket-development

Pocket Development

Precise subagent delegation for task-by-task development execution. POCKET ensures every delegation has a complete contract (Pocket Packet) that specifies exactly what must be done, how to verify it, and when to escalate.

Core principle: Every delegation is a contract. The packet is the contract. No packet, no spawn. Read execution-plan/index.md once to understand execution flow and dependencies, then open individual task files (execution-plan/tasks/T*-*.md) on demand when a task is ready to execute.

Startup: Initialize Execution Log

Run this before the first task, every session:

npx -y pocketto-pi log init "<plan_dir>" --json --contract 2

No install step, PATH setup, or shell-specific guard — npx resolves the cross-platform binary and log init is idempotent, so this is safe to run unconditionally every session. Replace <plan_dir> with the folder containing your execution plan (e.g. docs/pocket/plans/2026-05-08-auth-refactor).

• No log.json yet → creates it from the plan files in that directory
• log.json exists but tasks missing → migrates tasks into existing phases (status preserved)
• log.json already complete → reports "no migration needed" and writes nothing

Full command reference and update/close commands: see Execution Log section below.

---

When to Use

Use POCKET when ALL conditions are met:

• You have an implementation plan with 1+ tasks
• Tasks can be executed one-by-one (not requiring tight coupling)
• You need to delegate work to subagents

Task count does not gate eligibility. pocket-planning routes every plan through pocket-structuring, which accepts any task count, so a one-task plan reaches here as a legitimate Pocket plan. It is simply the degenerate case of SOLO — a group resolved to size 1 — and runs the normal Entry Gate, packet, audit, and phase-pass path. Do not bounce it to hotfix: hotfix is an entry-routing choice for small, clear work, not an escape hatch once a full spec and plan already exist.