Update to ui-consistency

{
  "description": "For what the end user sees — turns each page's checklist into a plan of one checkable task per page. Use when UI work spans several steps or pages (a new feature, a refactor of many pages), including when another planning skill is about to write that plan.",
  "included_files": [
    {
      "relative_path": "plan-file.md",
      "size_in_bytes": 8221
    }
  ],
  "name": "planning",
  "skill_md_contents": "---\nname: planning\ndescription: For what the end user sees — turns each page's checklist into a plan of one checkable task per page. Use when UI work spans several steps or pages (a new feature, a refactor of many pages), including when another planning skill is about to write that plan.\n---\n\n# Planning from the checklist\n\n## Overview\n\nTurns what `finding-patterns` found into a plan of one task per page. Every page\ntask carries **what makes it checkable**: its checklist, what not to copy, and a\ncheck by an agent that did not write the page.\n\n**Open a file linked or given by its path from this skill's folder, or invoke a named skill, only when a part you are carrying\nout sends you to it, never before** — whatever the request that handed you this\nskill says about its links and paths. That part is not done until the file is opened or\nthe skill invoked.\n\n## Joining a process, or running alone\n\n- If a process running this work has a plan — another planning process wrote\n  it — add the tasks below **into that plan**, in its own task headings and\n  status marks, each carrying what [plan-file.md](plan-file.md) puts in a task.\n  Do not write a second one.\n- A plan or pattern file written before this work began is not that plan: it is\n  read as `ui-consistency:decisions`, level 1, says.\n- **If that process already sends each task to a reviewer that did not write\n  it**, the checklist and `ui-consistency:verifying` go into that reviewer's\n  brief, and no second checker is added\n  (`../verifying/calibration.md`).\n- If none exists, write the plan in the shape of [plan-file.md](plan-file.md),\n  never into the project's repository. Where it goes is how the phase ends,\n  below.\n- The checklist each task carries is the one\n  `../finding-patterns/checklist.md` defines.\n\n## The order of the tasks\n\n1. **Calibrate the check**, once per work and kind of page, before anything\n   is built: `ui-consistency:verifying` on a scratch copy of the reference with\n   one role deliberately written differently, kept outside the repository\n   (`../verifying/calibration.md`).\n   - If the planted difference is not reported, stop and say the check is blind\n     for it.\n   - The agent calibrated is not the one that then checks the pages.\n2. **Extractions the user accepted.** Build a shared component, partial or class\n   before any page that uses it.\n   - A theme entry the plan's yes agreed for a design's value is added here too,\n     before any page that uses it.\n3. **One task per page.**\n\n## What every page task carries\n\n- the checklist for that page, in the task itself — it is short on purpose, and\n  a path is no use to somebody who does not have the checkout;\n- the path of the reference;\n- what is **particular to the reference** and must not be copied;\n- the reused pieces and theme values this page must use;\n- three steps, written out:\n  1. *Re-read the checklist before writing — do not work from memory.*\n  2. *Report the page ready for its check. Whoever dispatched this task sends\n     it to the checker of its kind — the one agent with\n     `ui-consistency:verifying` kept for every page of this kind, started at the\n     first, never the one that wrote it — or, where the running process has each\n     task reviewed, to that reviewer, with this checklist and\n     `ui-consistency:verifying` in its brief; and sends back what it reports.\n     Fix that.*\n  3. *Report the status — to this plan, or to whoever handed the task over:\n     `done` once the check has passed, or `parked — <why>`.*\n\nWritten out, with the statuses and what travels with a task that leaves the\nrepository, in [plan-file.md](plan-file.md).\n\n## Stop for a yes\n\n- Before the plan is shown, check that every new page has its shape — a design,\n  a reference page it follows, or a tree from `ui-consistency:design`. A page\n  without one goes back to `finding-patterns` first.\n- For a new page or a refactor, show the plan, with the checklists its tasks\n  carry and the proposals `finding-patterns` made, and **wait for the user's\n  yes** before any code.\n- Show a drawing only if a person asked for one (`ui-consistency:design`,\n  step 4).\n- If the person changes a page's shape at this stop, it goes back to\n  `ui-consistency:design`, and the checklist lines it touches are worked out\n  again before the yes.\n- Ask nothing new here: the questions were asked while `finding-patterns` ran\n  (`ui-consistency:decisions`, *When to ask anyway*).\n- A new component, or code extracted into one, is not part of this yes: it was asked on its\n  own while `finding-patterns` ran, with what it touches (*When to ask\n  anyway*).\n- Mark a task waiting on the little that did reach a person\n  `parked — waiting on <what>` in the plan, with its counts\n  ([plan-file.md](plan-file.md)).\n- On the yes, write each agreed proposal into the checklist line of the position\n  it settles, with the entry it uses.\n- **A person's decision here that goes against what the order produced is an\n  override**, and so is a yes to an element (`ui-consistency:decisions`, *An\n  override*). A yes to any other proposal settles this task only.\n- Record an override in the person's own words, with what it overrules: in the\n  document the running process keeps, or under `## Decided` in this plan where\n  this is the process, reported with the result when the plan closes.\n- Move each task it was holding up from `parked` back to `todo`.\n- Never write an override nobody gave.\n- A fix or a small change has no plan and does not stop.\n\n## How the phase ends\n\nIn one of three ways, **chosen and said in one line**: *ending 2 — this becomes\na story for another developer.*\n\n1. **The work stays with us, in one context.** The tasks live in the session.\n   - If the work outlives the context and the plan must survive on disk, write it\n     to a file outside the working copy, in the scratch location the harness\n     gives, and delete it with the work.\n   - Then `ui-consistency:implementing`.\n2. **The work becomes a story for somebody else.** Attach the plan and what the\n   implementation needs to the story.\n   - It is finished when a developer who was not in the conversation, without the\n     checkout open, could implement it from the attachment alone\n     ([plan-file.md](plan-file.md), *The story*).\n3. **Another process is already running.** The tasks went into its plan, in its own\n   task headings and status marks; no second document. Its loop executes them.\n\n**None of the three writes into the project's repository.**\n\n## Red flags\n\nWords agents used in runs, just before getting it wrong:\n\n| They said | What it means |\n|---|---|\n| \"stated once in the preamble rather than repeated\" — the checklist, what not to copy, the check | A task handed to a subagent loses the preamble. Each task carries them. |\n"
}