Plan Work

Contributors🕹️Paul Atkins, Myles Henaghan

Plans should include:

• clear objective and scope
• risk-ordered execution
• explicit dependencies
• acceptance and exit criteria
• evidence logging checkpoints

Effort sizing

Route to the correct scale by plan lifecycle stage — see effort-scales.yaml.

Stage	Scale	Skill
Gap analysis, remediation draft, sprint/Jira sizing	Wall-clock T-shirt (Trivial / Small / Medium / Large)	remediation-plan
Active WIP execution, progress burn-down	Fibonacci (1–13) + *.effort.json	plan-effort-estimate

Planning phase — size tasks for human team capacity and stakeholder timelines. Decisions that block work are tracked separately (not as effort).

Execution phase — when the plan goes WIP, create a *.effort.json sidecar beside the plan markdown, re-size steps with Fibonacci points, and run summarize-effort.mjs for deterministic progress totals. Use the indicative mapping in the taxonomy as a starting point only — re-size for AI-assisted delivery context.

Status presentation follows plan-status.yaml.

WIP document layout

When a plan enters active execution, follow the scan-first layout in plan-effort-estimate/references/plan-layout.md and copy the skeleton from wip-plan-template.md.

Fixed top-of-doc order after title/metadata:

1. 👀 progress block + phase status table (summarize-effort.mjs --markdown-top)
2. Recent progress (dated, evidence-based)
3. Goal (one paragraph)
4. Plan body
5. Effort breakdown at bottom (--markdown-breakdown)