WIP plan layout (👀 top summary)

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

Document order

# Plan title

Sub-plan / Status / Owner / Related plans

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

## Overview / Goal              ← what is this?
## Why now / Sequencing         ← why are we doing it?
… plan body …
## Risks / Open questions / Next actions

## Effort breakdown             ← near bottom (script: --markdown-breakdown)
{watermark to skill + effort.json}
{phase step tables}
{phase rollup table}

## References                   ← optional; after effort breakdown is OK

What goes where

Section	Content	Source
👀 top summary	Percent, effort done/total, steps done/total, remaining, anchor link	summarize-effort.mjs --markdown-top
Plan body	Goals, architecture, phases, decisions, risks	Human-authored
Effort breakdown	Step tables with Done / Left columns	summarize-effort.mjs --markdown-breakdown
Scale	Never inline — link to references/scale.md via skill watermark	Skill only

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 (`hoen-library` → `library/skills/plan-effort-estimate/` → `references/scale.md`). Re-run `summarize-effort.mjs --markdown-breakdown` after updates._

Refresh workflow

1. Edit *.effort.json beside the plan.
2. Run --markdown-top → paste over the top ## 👀 {percent}% complete block.
3. Run --markdown-breakdown → paste over ## Effort breakdown section.
4. Do not hand-calculate totals.