WIP plan layout (👀 scan-first)¶

Plans with effort tracking follow a fixed scan-first order at the top of the doc. Do not repeat the Fibonacci scale table in the plan — watermark to the plan-effort-estimate skill instead.

Full skeleton: wip-plan-template.md.

Document order¶

# Plan title

Sub-plan / Status / Owner / Related plans

## 👀 {percent}% complete          ← script: --markdown-top
{effort · steps · remaining}
Phase rollups: …
[Effort breakdown ↓](#effort-breakdown) · {effort.json} · scale watermark
### Phase status                   ← phase rollup table (in --markdown-top)

## Recent progress ({date})       ← human-authored; evidence-based
## Goal                             ← human-authored; one paragraph + scope boundary

… plan body (decisions, architecture, phased delivery, risks, open questions) …

## Effort breakdown                 ← script: --markdown-breakdown
{watermark to skill + effort.json}
{per-phase step tables}
{phase rollup table — duplicate of top for detail anchor}

## References                      ← optional; after effort breakdown is OK

What goes where¶

Section	Content	Source
Title block	`# Title`, sub-plan link, `Status:`, `Owner:`	Human-authored
👀 top summary	Percent, effort done/total, steps done/total, remaining, watermark	`summarize-effort.mjs --markdown-top`
Phase status table	Phase \| Effort \| Done \| Left \| Progress	`summarize-effort.mjs --markdown-top` (included)
Recent progress	Dated changelog; 3–6 bullets max; cite evidence	Human-authored
Goal	Outcome and scope boundary in one paragraph	Human-authored
Plan body	Architecture, phased delivery, decisions, risks	Human-authored
Effort breakdown	Per-step tables with Done / Left columns + phase rollups	`summarize-effort.mjs --markdown-breakdown`
Scale	Never inline — link via skill watermark	Skill only

Recent progress¶

Heading: ## Recent progress (YYYY-MM-DD) — use today's date when updating.
Lead with what was validated or landed, not intentions.
Call out still open exit criteria in one line if the active phase is not done.
Keep it short — detail belongs in step notes in *.effort.json or the plan body.

Goal¶

One ## Goal section immediately after Recent progress.
State the outcome, the primary constraint, and what is explicitly out of scope.
Do not duplicate the 👀 metrics or phase table here.

Watermark (copy verbatim pattern)¶

Top (short):

[Effort breakdown ↓](#effort-breakdown) · [`plan.effort.json`](./plan.effort.json) · scale: HoEN library **plan-effort-estimate** skill

Breakdown header (one line, italic):

_Sourced from [`plan.effort.json`](./plan.effort.json). Fibonacci scale: HoEN library **plan-effort-estimate** skill. Re-run `summarize-effort.mjs --markdown-breakdown` after updates._

Refresh workflow¶

Edit *.effort.json beside the plan.
Run --markdown-top → paste over the ## 👀 {percent}% complete block through ### Phase status table.
Update ## Recent progress and ## Goal if needed.
Run --markdown-breakdown → paste over ## Effort breakdown section.
Do not hand-calculate totals.