@erclx/canon 5.43.0 → 5.44.0

package/claude/skills/script-screencast/SKILL.md

@@ -0,0 +1,70 @@
+---
+name: script-screencast
+description: Drafts a screencast script with pre-seeded beats, defaults, and decisions to `demos/<slug>/beats.md`. Reads project context, asks four discovery questions with proposed defaults, then writes a shippable draft. Use when asked to "draft a screencast", "write a recording script", "plan a demo video", or "scaffold a screencast for X". Do NOT re-invoke to refine an existing draft. Re-running overwrites. Edit the draft file directly.
+metadata:
+  family: generate
+---
+
+# Script screencast
+
+## Guards
+
+- If no topic is provided, stop: `❌ No screencast topic. Describe what you are recording.`
+- Draft, then hand off. Do not edit video, generate captions, or drive the application, since a recording is `record-screencast`'s job. Name it as the next step and stop.
+- Stack-agnostic in the draft. Never name a recording tool, an editing tool, a font, or a window manager.
+- Keep selectors, URLs, wait conditions, and timings out of the beats, since the compiler adds those four in a plan of its own and a beat carrying them stops being readable
+
+## Step 1: read the project context
+
+Read these in parallel from the project root, skipping any that do not exist:
+
+- `CLAUDE.md`: behavior rules and project pitch
+- `canon/REQUIREMENTS.md`: feature scope, non-goals, audience hints
+- `.canon/tasks/index.md`: current scope
+- Recent commits via `git log --oneline -20 2>/dev/null || echo "FALLBACK"`: what shipped recently is usually the recording subject.
+
+## Step 2: discovery with proposed defaults
+
+Ask exactly four questions in chat. Each carries a proposed default derived from Step 1. The user confirms, overrides, or says "use defaults" to accept all.
+
+```markdown
+**Discovery:**
+
+1. Audience: proposing technical peers. Override?
+2. Length: proposing 75-90s. Override?
+3. Hero moment: proposing <best guess from context, or "the single thing that has to land">. Override?
+4. What to cut: proposing <best guess, or "anything that is not the hero moment">. Override?
+```
+
+Wait for answers before drafting. Do not infer silence as acceptance.
+
+## Step 3: derive the slug
+
+Build a 2-to-4-word kebab-case slug from the topic and discovery answers. Examples: `auth-flow-redesign`, `cli-onboarding`, `inline-edit-launch`.
+
+## Step 4: write the draft
+
+Create `demos/<slug>/beats.md` at the project root, creating the folder if it does not exist. The file is committed with the rest of the demo's sources, so a recording can be rebuilt from the folder alone.
+
+### Fill the template
+
+Write all nine sections from `${CLAUDE_SKILL_DIR}/references/beats-template.md`, read on reaching this step. Pre-seed every section with concrete content so the draft ships as-is, and the user edits down rather than fills blanks. A run stopped at discovery skips it.
+
+Load `canon:video-craft` for every zoom and caption value the draft names, and report it rather than proceeding silently when it does not resolve.
+
+## Step 5: output
+
+Print the file path on its own line and a one-line summary. Do not paraphrase the path into prose.
+
+```markdown
+📝 Wrote demos/<slug>/beats.md
+
+Draft has 5 beats and pre-seeded defaults. Edit the beats, the resolved decisions, and the wrap.
+
+To record it rather than shoot it by hand:
+record-screencast demos/<slug>/beats.md
+```
+
+Name the skill and stop there. Do not compile the draft, do not run it, and do not generate captions. The operator edits the beats first, and the compiler reports which selectors and URLs they still owe it.
+
+Say so plainly if `canon demo compile` is not available, rather than driving the application some other way. The command ships with the CLI and the skills ship with the plugin, so a project carrying one and not the other is a real state.

package/claude/skills/{draft-screencast → script-screencast}/references/beats-template.md

@@ -1,11 +1,11 @@
 ---
 title: Beats template
-description: The nine-section template draft-screencast writes to demos/<slug>/beats.md, pre-seeded so the draft ships as-is
+description: The nine-section template script-screencast writes to demos/<slug>/beats.md, pre-seeded so the draft ships as-is
 ---
 
 # Beats template
 
-Applies to the draft `draft-screencast` Step 4 writes. Fill every placeholder from the project context and the discovery answers. The template states no zoom or caption value, since each traces to a source `canon:video-craft` records.
+Applies to the draft `script-screencast` Step 4 writes. Fill every placeholder from the project context and the discovery answers. The template states no zoom or caption value, since each traces to a source `canon:video-craft` records.
 
 ## Template
 

package/claude/skills/search-craft/REQUIREMENT.md

@@ -7,7 +7,7 @@ description: Why a session needs a thinking step before an outside search, deriv
 
 ## Gap
 
-Without this skill, a session reaching outside the project runs one generic `WebSearch` and takes what ranks highest. Nothing in the toolkit says how to search, and the two procedures that require an outside source, `plan-groundwork` and `draft-doc`'s wiki kind, give no route to one.
+Without this skill, a session reaching outside the project runs one generic `WebSearch` and takes what ranks highest. Nothing in the toolkit says how to search, and the two procedures that require an outside source, `plan-groundwork` and `write-doc`'s wiki kind, give no route to one.
 
 The miss is measured. On 2026-10-02 two queries ran twice each with identical text, once open and once with `allowed_domains` set to authorities the session derived itself with no list to consult.
 
@@ -30,7 +30,7 @@ Access is a second gap a session cannot derive. Probed on 2026-10-02, Reddit ref
 - Prefer a public API over a fetched and summarized page where one exists, since the API returns the dates, authors, and identifiers a citation needs
 - Carry a dated access note grown only from a failure a session hit, and stop to ask the operator before any paid or logged-in route
 - Close with the practice skill's excuses, red flags, and closing checklist, answering "the model already knows the good sites" and "one search was enough"
-- Be loaded from the sourcing steps of `plan-groundwork` and `draft-doc`'s wiki kind, each reporting when the skill does not resolve
+- Be loaded from the sourcing steps of `plan-groundwork` and `write-doc`'s wiki kind, each reporting when the skill does not resolve
 
 ## Must not
 
@@ -42,7 +42,7 @@ Access is a second gap a session cannot derive. Probed on 2026-10-02, Reddit ref
 ## Out of scope
 
 - The form a citation takes: the procedure or standard writing it
-- A Claude Code subject: a direct fetch of `https://code.claude.com/docs/llms.txt` and the `.md` page it names, as `draft-doc`'s wiki sourcing step already does
+- A Claude Code subject: a direct fetch of `https://code.claude.com/docs/llms.txt` and the `.md` page it names, as `write-doc`'s wiki sourcing step already does
 - Image generation, which makes a picture rather than finding a source
 - Loading on every web search rather than on a research-shaped request: a hook matching `WebSearch`, planned on its own
 - Whether a session already scopes searches without the skill, which only a run on a fresh research request without it would show
@@ -54,4 +54,4 @@ Access is a second gap a session cannot derive. Probed on 2026-10-02, Reddit ref
 - No `Skill` call fired, so the description did not route a plain research request to the body.
 - The run searched four times with no domain filter, naming authors and journals from recall, then fetched the papers' own pages. It never named the field, so the scenario's field pattern failed and the arm went red on one of its assertions.
 
-The arm shows the trigger is the gap rather than the body: a session that never loads the skill cannot follow it. The pointers from `plan-groundwork` and `draft-doc`'s wiki kind reach only those procedures, and the hook matching `WebSearch` is the route for every other search. One run on one model shows the miss exists and does not size it.
+The arm shows the trigger is the gap rather than the body: a session that never loads the skill cannot follow it. The pointers from `plan-groundwork` and `write-doc`'s wiki kind reach only those procedures, and the hook matching `WebSearch` is the route for every other search. One run on one model shows the miss exists and does not size it.

package/claude/skills/search-craft/SKILL.md

@@ -87,6 +87,6 @@ These flags fire after the search has run.
 ## What this delegates
 
 - The form a citation takes: the surface writing it, such as the standard the procedure writes to
-- A Claude Code subject: a direct fetch of `https://code.claude.com/docs/llms.txt` and the `.md` page it names, as `draft-doc`'s wiki sourcing step does
+- A Claude Code subject: a direct fetch of `https://code.claude.com/docs/llms.txt` and the `.md` page it names, as `write-doc`'s wiki sourcing step does
 - Generating an image: whatever draws the surface, since making one is not search
 - Access code a session needs repeatedly: a `canon` verb, never a script in this skill

package/claude/skills/target-setup/SKILL.md

@@ -183,6 +183,7 @@ After the chain, report as well:
 - Any domains or scripts that failed
 - Any detection gaps surfaced during resolve
 - Claude Code plugins as an onboarding step this chain does not cover, so a clean result does not read as onboarding complete
+- `/canon:write-doc README.md` when the root `README.md` is missing or carries no H1 naming the project, and nothing when it is authored
 
 A resolved name and a fallback read alike once written, so the preview marks the
 fallback rather than this report. The preview is the last point before the first

package/claude/skills/task-board/SKILL.md

@@ -67,10 +67,12 @@ Write `.canon/tasks/vXX.Y-<slug>.md` under the claimed label, reading the file f
 
 A task file with no row is a dropped task, so name its surface in the same pass that creates it. The test and both file shapes are in `${CLAUDE_SKILL_DIR}/references/board.md`.
 
-| Task                                        | Surface                                                                                                                         |
-| ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
-| Plausibly planned within the next few waves | A row under `## Needs a plan` in `.canon/tasks/priority.md`, positioned against the rows there, with the reason in `Waiting on` |
-| Anything else                               | A line in `.canon/tasks/backlog.md`, which is unordered                                                                         |
+| Task                                        | Surface                                                                                                                                   |
+| ------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| Plausibly planned within the next few waves | A row under `## Needs a plan` in `.canon/tasks/priority.md`, through `canon tasks place <stem> --group needs-a-plan --waiting "<reason>"` |
+| Anything else                               | A line in `.canon/tasks/backlog.md`, which is unordered                                                                                   |
+
+Position the row against its siblings with `--before <stem>` or `--after <stem>`, and state what it ranks against in the reason.
 
 ### Check for a live orchestrator
 
@@ -80,11 +82,11 @@ Check the roster before writing either file. Read `canon sessions list --self --
 - Its `name` starts with `orchestrator-`, the convention every hand-launched controller here uses, which excludes every `worker-` and `planner-` session
 - Treat a refusal from either call the same as a roster read that failed
 
-| Roster read                                                                | Act                                                                                                          |
-| -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
-| **Found**                                                                  | Write neither file. Report the surface and reason, and message that session so it places the row itself      |
-| **Not found**, and this session's name starts with `worker-` or `planner-` | Write neither file, since both role bodies ban a board write. Report the row and its surface.                |
-| **Not found otherwise**, or the read fails                                 | Write the row directly, through the same heredoc route as the file. A failed read looks like a solo project. |
+| Roster read                                                                | Act                                                                                                     |
+| -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- |
+| **Found**                                                                  | Write neither file. Report the surface and reason, and message that session so it places the row itself |
+| **Not found**, and this session's name starts with `worker-` or `planner-` | Write neither file, since both role bodies ban a board write. Report the row and its surface.           |
+| **Not found otherwise**, or the read fails                                 | Place the row through `canon tasks place`. A failed read looks like a solo project.                     |
 
 Say which branch fired and why in the report. A placement with no stated reason is one the next sweep re-derives from nothing.
 

package/claude/skills/task-board/references/board.md

@@ -70,28 +70,31 @@ Group tasks by readiness rather than by status, one row per task, under the colu
 
 Readiness is three groups under fixed headings, `## Run now`, `## Up next`, and `## Needs a plan`, in that order. A task belongs to exactly one, and the tests are read in order.
 
-| Group             | Test                                                                                   |
-| ----------------- | -------------------------------------------------------------------------------------- |
-| `## Run now`      | A written plan covers every open outcome, and nothing stated keeps the task from start |
-| `## Up next`      | A written plan exists, and the `Waiting on` column names why the task cannot start     |
-| `## Needs a plan` | Everything else. No plan, or a plan that no longer describes the work                  |
+| Group             | Test                                                                                 |
+| ----------------- | ------------------------------------------------------------------------------------ |
+| `## Run now`      | A worker was dispatched on it, under a written plan covering every open outcome      |
+| `## Up next`      | A written plan exists and no worker holds it yet, and `Waiting on` names what is due |
+| `## Needs a plan` | Everything else. No plan, or a plan that no longer describes the work                |
 
 The names are the contract. A board grouped by readiness under names of its own reads as empty to anything counting rows under a heading, so add no fourth group.
 
+### Writing the board
+
+Every write goes through `canon tasks place`, `promote`, `move`, or `block`, each reading the file once, rendering the columns the template fixes, and writing it once. `plan-link` promotes a parked row the same way. Only `Waiting on` is typed, since every other cell derives from the task and its live plans.
+
 ### What blocks a run
 
 A collision with running work blocks a task only where no merge settles it, being a contract, a relocation, or a sweep. A shared file alone is none, since the branch merging second rebases.
 
-- A worker is handed a task from `## Run now` alone, and its `Touches` column states the set to read
-- Each group's columns follow from its test. Neither half of the `## Run now` test is checkable without the file set and the plan beside the task.
+- A dispatcher picks from `## Up next` and runs `canon tasks promote` once the launch succeeds
+- Each group's columns follow from its test. Neither half of the `## Up next` test is checkable without the file set and the plan beside the task.
 
 ### The `Touches` cell
 
-A `Touches` cell is copied from its plan's list, so it states what the branch sets out to write rather than a bound on it. A branch outgrows it while the row still reads as it did at dispatch.
+A `Touches` cell is the first three paths of its plan's `**Files to touch:**` and a count of the rest, the union in line order for a sliced task. It states what the branch sets out to write, and a running branch outgrows it.
 
-- Once a branch runs, correct the cell from the diff rather than the plan, which is the prediction that already went stale
-- `canon tasks plan-reach <plan>` reads that diff against every live plan and every cell in the group
-- The row's owner writes the correction. A worker never edits this board.
+- `canon tasks plan-reach <plan>` reads the current reach off the branch's diff
+- Change the plan's list to change the cell. A worker never edits this board.
 
 ### Cell width
 
@@ -118,7 +121,7 @@ The `Waiting on` column under `## Up next` carries the reason in one of three fo
 | Sibling task       | That task                                                                     |
 | External condition | The condition and what would satisfy it                                       |
 
-Naming what would satisfy a condition separates a blocked row from one nobody examined, so a condition with no way out fails the test. The header text is the contract, since a reader resolves the column by header rather than position.
+Naming what would satisfy a condition separates a blocked row from one nobody examined, so a condition with no way out fails the test. The header text is the contract, since a reader resolves the column by header rather than position. A cell renders at most 120 characters, a link counting as its label alone, and the verbs refuse a longer one.
 
 ### The needs-a-plan cell
 

package/claude/skills/teach-workspace/SKILL.md

@@ -183,7 +183,7 @@ Read `${CLAUDE_SKILL_DIR}/references/promotion-fold.md` for how each block lands
 Lesson:    .canon/teach/<nn>-<topic>/lessons/<nnnn>-<slug>.html
 Reference: .canon/teach/<nn>-<topic>/reference/<slug>.md
 Record:    .canon/teach/<nn>-<topic>/learning-records/<nnnn>-<slug>.md
-Figure:    <drawn through draft-figure, or the one-line reason prose carries it>
+Figure:    <drawn through draw-figure, or the one-line reason prose carries it>
 Progress:  <n> of <m> success lines met
 Open:      [<the url the serve verb reported>](<the same url>)
 ```

package/claude/skills/teach-workspace/references/lesson-craft.md

@@ -51,8 +51,8 @@ Every element competes with the material for attention.
 Decide the figure once per lesson, before writing the body.
 
 1. Name the one relationship, boundary, path, or before-and-after the lesson is about. A lesson about none ends here, with `Figure: none, <why it names no structure>` on the reply.
-2. Hold it against the bar in `${CLAUDE_SKILL_DIR}/../draft-figure/references/figures.md`, which also carries the drawing rules.
-3. Draw it through `canon:draft-figure` into a `raw` block before the quiz, never inside it or after its feedback, which breaks the stepper's gating. Report an unresolved skill rather than drawing.
+2. Hold it against the bar in `${CLAUDE_SKILL_DIR}/../draw-figure/references/figures.md`, which also carries the drawing rules.
+3. Draw it through `canon:draw-figure` into a `raw` block before the quiz, never inside it or after its feedback, which breaks the stepper's gating. Report an unresolved skill rather than drawing.
 4. Or write one line on why prose carries it better, such as a structure an earlier lesson gave.
 
 A structure lesson takes step 3 or 4, never neither. Put the outcome on the reply's `Figure:` line, off the lesson page. Never draw to satisfy the step, or on every section (`## Restraint`).

package/claude/skills/ui-checklist/SKILL.md

@@ -43,6 +43,8 @@ Write each box so a session driving the running app can run it without guessing:
 | Taste | End the line with `(taste)` when the result is a judgment of look or feel. A driver reports such a box as needing a person's eyes rather than passing it.                       |
 | Setup | State inline any setup the page does not open in. End the line with `(local only)` when a hosted preview cannot reach that state, such as a stopped service or a seeded record. |
 
+When the plan cites `canon/design/<surface>/` under `**Design references:**`, name the reference as the comparison on each box for that surface, such as "→ matches `canon/design/<surface>/` in light and dark". The reviewer then judges the build against the accepted design instead of against taste.
+
 The checkbox stays `- [ ]` followed by the action and the result, since the evidence comment reads boxes by that shape. Only the UI reviewer ticks a box, stamping it with the commit it passed at, and the comment carries that tick forward only while the head it names is current.
 
 ## The missing-test list

package/claude/skills/write-doc/REQUIREMENT.md

@@ -0,0 +1,46 @@
+---
+name: write-doc
+description: Why a brand-new project document needs its kind's standard, a catalog collision check, and a confirm step, not the rewrite and refresh paths docs-sync and context-fold already own
+---
+
+# Write doc requirement
+
+## Gap
+
+Without this skill, a session drafting a document that has no prior version either invents a shape from memory or reaches for a rewrite or refresh surface. `docs-sync` and `context-fold` read an existing document and a diff, and a document that never existed has neither, so they report the request as unrelated to any change. Either way the document ships with no read of the standard its kind answers to and no check against the catalog for a sibling already covering the same ground under a different name.
+
+The same procedure ran as five skills, one per kind, each restating the read, the collision check, the confirm, and the write. They drifted on their own cadence, and five descriptions competed for one trigger, writing a new document.
+
+## Must
+
+- Resolve the kind from the destination the request names, and ask rather than defaulting when it names none, since a document in the wrong surface is invisible where a reader looks for it
+- Load exactly one kind reference per run, so every step that differs by kind lives in one file and the shared procedure in one body
+- Read the kind's standard before drafting, since its frontmatter contract and its reader questions make the document arguable against a sibling
+- Check the catalog by exact name and by title and description, since a subject can be covered under a name the request does not guess
+- Confirm the resolved path, the kind's detections, and the full content with the user before writing, since placement and detection are judgment calls with no diff to preview them against
+- Regenerate the catalog of the folder the document landed in, where the kind keeps one, so the next run's collision check sees it
+- Draft a README from the template for every detected project type and combine them, never the closest one, since a project that is a CLI and a plugin owes its reader both
+- Carry each kind's own musts in its reference: the root check for context, both placement tests and a fetched source for the wiki, and project detection and rendered-value badges for the readme
+
+## Must not
+
+- Rewrite, refresh, or sync a document that already exists. A collision refuses toward the surface that owns the existing document.
+- Hand-edit an `index.md`. It regenerates from sibling frontmatter, and a hand edit is overwritten on the next regen.
+- Substitute recall for a failed fetch on the wiki kind, or invent an image or a placeholder path on the readme kind.
+- Build a hand-drawn diagram loop for a docs page.
+- Widen the wiki's folder split to admit a subject its second placement test rejects. That is a change to the standard, argued there.
+- Assume this skill's routing needs no check. One description now covers four triggers, and a ranking over descriptions is a proxy for how Claude Code routes, so a review some months in should read real invocations back.
+
+## Guards
+
+- No subject given, for any kind but the readme: stop and ask what the document should cover.
+- No destination named: ask which kind rather than defaulting to `docs/`.
+- Every other guard is the kind's own, stated in its reference.
+
+## Out of scope
+
+- Rewriting or syncing an existing `docs/` page or an authored README against a diff: `docs-sync`
+- Refreshing an existing context entry: `context-fold`
+- Drafting a governance rule: `create-rule`
+- Drawing a figure or a diagram for a document: `draw-figure`
+- Voice, rhythm, punctuation, and formatting in the drafted document: the `write-human` skill and the markdown standard

package/claude/skills/write-doc/SKILL.md

@@ -0,0 +1,83 @@
+---
+name: write-doc
+description: Drafts one brand-new project document from scratch against the standard for its kind, picking the kind from where it lands, a `docs/` page, a `canon/context/` entry, a wiki reference page, or a README.md. Checks the catalog for a name or topic collision, places it, confirms with the user, then writes. Use when asked to "write a new docs page for X", "write a context entry for X", "write a wiki page for X", or "write a README" where none exists yet. Do NOT use to rewrite or sync an existing page or README against a diff, which is `docs-sync`, or to refresh a context entry, which is `context-fold`.
+metadata:
+  family: generate
+---
+
+# Write doc
+
+Drafts one brand-new project document end to end: resolve its kind, read the standard that kind answers to, check the catalog for a collision, place it, draft, confirm with the user, then write.
+
+## Resolve the kind
+
+Each kind has one standard and one reference. Load the reference for the resolved kind and no other, since every step below that differs by kind lives there.
+
+| Kind    | Lands at                                                 | Standard                                                    | Reference                                     |
+| ------- | -------------------------------------------------------- | ----------------------------------------------------------- | --------------------------------------------- |
+| docs    | a page under `docs/`                                     | `${CLAUDE_SKILL_DIR}/../docs-sync/references/docs.md`       | `${CLAUDE_SKILL_DIR}/references/docs.md`      |
+| context | an entry under `canon/context/`                          | `${CLAUDE_SKILL_DIR}/../context-fold/references/context.md` | `${CLAUDE_SKILL_DIR}/references/context.md`   |
+| wiki    | a reference page on a subject owned outside this project | `${CLAUDE_SKILL_DIR}/references/wiki.md`                    | `${CLAUDE_SKILL_DIR}/references/wiki-kind.md` |
+| readme  | a `README.md`, at the root or in a folder                | `${CLAUDE_SKILL_DIR}/../docs-sync/references/readme.md`     | `${CLAUDE_SKILL_DIR}/references/readme.md`    |
+
+- Read the kind off the destination the request names: a path, a folder, or the document's own name, such as "a context entry" or "a wiki page".
+- Ask which kind when the request names no destination, offering the candidates the subject fits with the likeliest first
+- Never default to `docs/` without saying so, since a subject documented in the wrong surface is invisible to the session that looks for it in the right one
+- If no subject is given for any kind but readme, stop: `❌ No subject given. Name what this document should cover.`
+- A README covers the project or the folder it sits in, so its subject is the target path
+
+## Read
+
+Read these in parallel, from the project root where a path is relative:
+
+- The kind's standard from the table above: the reader the document serves, its frontmatter, its structure, and what it links out to rather than restates
+- `${CLAUDE_SKILL_DIR}/../markdown-craft/references/markdown.md`: punctuation and formatting for all generated text
+- The `write-human` skill: voice, rhythm, and sentence construction for all generated text
+- The kind's reference from the table above
+
+## Guards
+
+Run the guards the reference states before placing or drafting anything. Each one stops toward the surface that owns the case, and a stop writes nothing.
+
+## Placement
+
+Settle the path and check the catalog for a collision the way the reference states. An exact-name check alone misses a document already covering the subject under another name, so check the titles and descriptions of the catalog the placement step already reads, and stop the same way on a match.
+
+## Draft
+
+- Draft against the kind's standard, keeping its template and its section order.
+- Draft frontmatter where the standard requires it, then the body, following the reference for what the kind adds.
+- Write for a reader with no source open. Omit an expected section with nothing to put in it rather than padding it.
+
+## Confirm
+
+- Show the kind, the resolved path, whatever else the reference names for the preview, and the full drafted content before writing.
+- Confirm with the user, and wait for that answer rather than treating the tool permission dialog as the gate
+- The kind, the placement, and every detection the reference runs are judgment calls with no diff to preview them against, which is why the dialog cannot stand in
+
+## Write
+
+- Write the file at the confirmed path, creating the folder when it is absent unless the reference narrows that.
+- Run `canon markdown audit <path>` and fix every ban, density, and reference shape finding until a re-run reports none. The whole file is this run's draft, so every finding is its own.
+- Run `canon indexes regen <folder>` on the folder the reference names, so its `index.md` picks up the new document. Skip it where the reference says the kind keeps no catalog.
+
+## Response format
+
+### Preview
+
+**Kind:** `<docs | context | wiki | readme>`
+**Subject:** `<subject, or the target path for a README>`
+**Placement:** `<path>`
+<one line per preview field the reference names>
+
+```markdown
+<drafted frontmatter and body>
+```
+
+### After confirmation
+
+One line once the file is written and its audit reports nothing.
+
+```plaintext
+✅ Drafted: <path>
+```

package/claude/skills/{draft-doc → write-doc}/references/context.md

@@ -1,11 +1,11 @@
 ---
 title: Context kind
-description: The root check, guard, flat-file placement, three-question draft, and regen folder for a brand-new context entry, read by draft-doc once the request resolves to the context kind
+description: The root check, guard, flat-file placement, three-question draft, and regen folder for a brand-new context entry, read by write-doc once the request resolves to the context kind
 ---
 
 # Context kind
 
-`draft-doc` reads this file when the request resolves to an entry under `canon/context/`. An entry that already exists is refreshed by `context-fold`, never drafted here.
+`write-doc` reads this file when the request resolves to an entry under `canon/context/`. An entry that already exists is refreshed by `context-fold`, never drafted here.
 
 ## Root
 

package/claude/skills/{draft-doc → write-doc}/references/docs.md

@@ -1,11 +1,11 @@
 ---
 title: Docs kind
-description: The guard, placement, draft additions, and regen folder for a brand-new page under docs/, read by draft-doc once the request resolves to the docs kind
+description: The guard, placement, draft additions, and regen folder for a brand-new page under docs/, read by write-doc once the request resolves to the docs kind
 ---
 
 # Docs kind
 
-`draft-doc` reads this file when the request resolves to a page under `docs/`. A page that already exists is rewritten by `docs-sync`, never drafted here.
+`write-doc` reads this file when the request resolves to a page under `docs/`. A page that already exists is rewritten by `docs-sync`, never drafted here.
 
 ## Guards
 

package/claude/skills/{draft-doc → write-doc}/references/readme.md

@@ -1,11 +1,11 @@
 ---
 title: Readme kind
-description: The target default, authored-versus-scaffold guard, project detection, header block, and badges for a README.md, read by draft-doc once the request resolves to the readme kind
+description: The target default, authored-versus-scaffold guard, project detection, header block, and badges for a README.md, read by write-doc once the request resolves to the readme kind
 ---
 
 # Readme kind
 
-`draft-doc` reads this file when the request resolves to a `README.md`. An authored README is rewritten by `docs-sync`, never drafted here.
+`write-doc` reads this file when the request resolves to a `README.md`. An authored README is rewritten by `docs-sync`, never drafted here.
 
 The readme standard claims the voice of a repository-root README. `write-human` yields voice there and keeps rhythm, density, and the machine-tell catalog everywhere, the root README included.
 

package/claude/skills/{draft-doc → write-doc}/references/wiki-kind.md

@@ -1,11 +1,11 @@
 ---
 title: Wiki kind
-description: The root guard, both placement tests, catalog collision, sourcing from the owner, and vendor-folder regen for a brand-new wiki reference page, read by draft-doc once the request resolves to the wiki kind
+description: The root guard, both placement tests, catalog collision, sourcing from the owner, and vendor-folder regen for a brand-new wiki reference page, read by write-doc once the request resolves to the wiki kind
 ---
 
 # Wiki kind
 
-`draft-doc` reads this file when the request resolves to a wiki reference page. A page that already exists is edited against the same standard, never drafted a second time.
+`write-doc` reads this file when the request resolves to a wiki reference page. A page that already exists is edited against the same standard, never drafted a second time.
 
 The standard's `## Placement` section names the folder a page lands in and the vendor subfolder under it. Resolve both from the project root and call them `<wiki-root>` and `<vendor>` below, so the standard stays the one owner of the path.
 
@@ -19,7 +19,7 @@ The standard sets two tests and a page has to pass both. Run them before draftin
 
 | Test                                        | Fails on                                                                        | Refusal                                                                                                                                    |
 | ------------------------------------------- | ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
-| Owned outside this repository               | A subject describing how this repository works                                  | `❌ <subject> is owned by this project, so it belongs in the docs surface or a context entry. Re-run draft-doc naming that destination.`   |
+| Owned outside this repository               | A subject describing how this repository works                                  | `❌ <subject> is owned by this project, so it belongs in the docs surface or a context entry. Re-run write-doc naming that destination.`   |
 | Owned by the vendor the folder split covers | A third-party tool or a vendor-neutral concept, however reference-like it reads | `❌ <subject> is outside the wiki's folder split. Route it to the docs surface or a skill body rather than adding a second folder for it.` |
 
 On the first test, offer the docs or context kind of this skill. The standard names one owner and one subfolder for the second.

package/docs/agents/markdown-audit.md

@@ -45,8 +45,10 @@ A page marked `kind: reference` holds its opening, then `Output`, `Refusals`, an
 - A paragraph under a list item counts toward that bullet, never as a paragraph
 - A table, fence, list, heading, or bold section marker ends a run of paragraphs
 - A run whose every item opens with a bold label or a link is exempt, and numbered items never count
-- Only context entries, docs, skill bodies and references, tooling seeds and stack references, the wiki, `README.md`, and `CONTRIBUTING.md` take a finding
-- A bullet run gates everywhere those paths sit, and the rest gates under `GATED_PATHS` in `src/markdown/scope.ts`. Outside a canon checkout nothing gates.
+- Only context entries, docs, skill bodies, references, and requirements, tooling seeds and stack references, the wiki, `README.md`, and `CONTRIBUTING.md` take a finding
+- A bullet run gates on those paths, and the rest gates under `GATED_PATHS` in `src/markdown/scope.ts`. Outside a canon checkout nothing gates.
+
+A requirement is the one exception to both. It gates only once `GATED_PATHS` names its own file, never through its skill's prefix and never on a bullet run alone.
 
 Five measures report and never set the exit code on their own.
 

package/docs/agents/migrate.md

@@ -11,7 +11,7 @@ kind: reference
 | Verb               | Moves                                                                                                                                       |
 | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------- |
 | `rename`           | The retired `aitk` name. `--scope target` rewrites toolkit-owned folders only.                                                              |
-| `skill-names`      | Plugin skills off their `claude-` prefix and other retired names, with every citation                                                       |
+| `skill-names`      | Plugin skills off their `claude-` and `draft-` prefixes and other retired names, with every citation                                        |
 | `records`          | Session records from `.claude/` to `.canon/`, with every tracked citation                                                                   |
 | `surface-roots`    | `context/`, `wireframes/`, `ARCHITECTURE.md`, `REQUIREMENTS.md`, `DESIGN.md`, and the stamp folder from `.claude/` to `canon/`, by `git mv` |
 | `record-tree`      | Citations inside `.canon/` folders a session still follows: `diagrams`, `memory`, `plans`, `proposals`, `review`, `tasks`, `teach`          |
@@ -20,7 +20,7 @@ kind: reference
 | `record-layout`    | Review receipts, memory archives, feedback, renders, picks, and evidence into their current folders                                         |
 | `session-defaults` | The seeded session defaults into an existing `.claude/settings.json`: `Agent` and `Task` denied, auto memory off                            |
 
-- `skill-names` takes no `--scope` and skips the changelog and eval transcripts
+- `skill-names` takes no `--scope`, and skips the changelog, eval transcripts, and the pointer each renamed `draft-` skill leaves at its old name
 - `surface-roots` leaves `rules/`, `skills/`, `hooks/`, and `settings.json` where Claude Code reads them
 - `rule-layout` classifies each flat file against the stamp as clean, edited, or unclaimed. Clean and edited files move untouched, and an unclaimed name stays.
 - `record-layout` labels each evidence folder `(pick)` or `(evidence)` in the dry run

package/docs/target/migrations.md

@@ -46,9 +46,22 @@ Run it once, ahead of `canon gov sync` or `canon gov install`.
 
 ## Rename the skill citations, once
 
-Plugin skills dropped their `claude-` prefix, so `canon:claude-docs` answers as `canon:context-fold` and `canon:claude-tasks` as `canon:task-board`. The five per-kind drafters merged into `draft-doc`, and no pointer under an old name ships. <!-- canon-keep-retired -->
+Plugin skills dropped their `claude-` prefix, so `canon:claude-docs` answers as `canon:context-fold` and `canon:claude-tasks` as `canon:task-board`. The five per-kind drafters merged into `write-doc`, and no pointer under an old name ships. <!-- canon-keep-retired -->
+
+The seven `draft-` skills took verb-first names for what each makes. `canon migrate skill-names --write` carries a project across, and a pointer under each old name answers a typed invocation until it retires.
+
+| Old name           | New name                                        |
+| ------------------ | ----------------------------------------------- |
+| `draft-doc`        | `write-doc` <!-- canon-keep-retired -->         |
+| `draft-figure`     | `draw-figure` <!-- canon-keep-retired -->       |
+| `draft-identity`   | `design-identity` <!-- canon-keep-retired -->   |
+| `draft-slides`     | `make-deck` <!-- canon-keep-retired -->         |
+| `draft-and-pick`   | `pick-by-eye` <!-- canon-keep-retired -->       |
+| `draft-ready`      | `plan-ready` <!-- canon-keep-retired -->        |
+| `draft-screencast` | `script-screencast` <!-- canon-keep-retired --> |
 
 - `canvas` is now `canvas-board`. The sweep rewrites only `canon:canvas` and `skills/canvas`, so replace a bare prose mention by hand. <!-- canon-keep-retired -->
+- `draft-ready` is rewritten only as `canon:draft-ready` and `skills/draft-ready`, since bare it also describes a pull request. Replace a bare mention of the skill by hand. <!-- canon-keep-retired -->
 - `design-extract` and `sketch-design` are replaced by `canon:canvas-board`. <!-- canon-keep-retired -->
 - `review-branch`, `seed-sync`, `restate-plainly`, `bash-cli-script`, `canon-operator`, and `canon-rollout` have no successor <!-- canon-keep-retired -->
 - `create-standard`, `markdown-propose`, `memory-review`, `project-commands`, `repo-metadata`, and `ux-walkthrough` have no successor <!-- canon-keep-retired -->
@@ -108,7 +121,7 @@ From the registry the walk reports `historyUnavailable`, so check both paths by
 | `context-fold`    | `context`                                                     |
 | `canvas-board`    | `canvas`, `design`                                            |
 | `docs-sync`       | `docs`, `readme`                                              |
-| `draft-figure`    | `figures`, `mermaid`                                          |
+| `draw-figure`     | `figures`, `mermaid`                                          |
 | `create-rule`     | `rule`                                                        |
 | `create-skill`    | `skill`, `skill-paths`, `skill-practice`, `skill-requirement` |
 | `git-branch`      | `branch`, `slug`                                              |
@@ -119,8 +132,8 @@ From the registry the walk reports `historyUnavailable`, so check both paths by
 | `plan-groundwork` | `groundwork`, `groundwork-spikes`                             |
 | `plan-intake`     | `intake`                                                      |
 | `plan-feature`    | `plan`, `plan-lifecycle`                                      |
-| `draft-ready`     | `ready`                                                       |
-| `draft-doc`       | `requirements`, `wiki`                                        |
+| `plan-ready`      | `ready`                                                       |
+| `write-doc`       | `requirements`, `wiki`                                        |
 | `session-map`     | `session`                                                     |
 
 The `standard` name became `skill-reference.md` in `create-skill`.

package/docs/target/projects.md

@@ -57,7 +57,7 @@ Before the first feature session:
 
 1. Fill `canon/REQUIREMENTS.md` with the problem, goals, and non-goals. The seed's 600-word cap gates under `canon context audit`.
 2. For a UI project, write `canon/DESIGN.md` from the seed and name the stylesheet in its lead, or work the direction out with `canon:canvas-board`
-3. Optionally invoke `canon:draft-figure` for an architecture view. The Mermaid CLI downloads on first use.
+3. Optionally invoke `canon:draw-figure` for an architecture view. The Mermaid CLI downloads on first use.
 4. Start the feature loop in [AI workflow](../workflow/ai-workflow.md)
 
 ### Stack decision

package/docs/workflow/parallel-features.md

@@ -49,13 +49,14 @@ Merge order matters only when two branches touch the same file. Expect to rebase
 
 ## The task board
 
-`.canon/tasks/` is gitignored and resolves at the main worktree root, one file per task. A hook generates `index.md`, and `priority.md` carries execution order and blockers.
+`.canon/tasks/` is gitignored and resolves at the main worktree root, one file per task. A hook generates `index.md`, and `priority.md` carries execution order and blockers. `canon tasks place`, `promote`, `move`, and `block` write it, deriving every cell but `Waiting on`.
 
 `canon tasks validate` reports and never writes:
 
 - A row's cell count must match its header, and a `## Needs a plan` row stating its position is checked against where it sits
 - Every plan pointer resolves, every task file is named once, and every ready row names its files
-- A parked row is reported when its cited task reached the trunk
+- A parked row is reported when its cited task reached the trunk, whether the cell links it or names its bare label
+- A group header must be the columns the group owns, a `Touches` cell must match its plan, and a `Waiting on` cell renders at most 120 characters
 
 `canon:task-board` creates a task file, and `canon:task-complete` marks outcomes. The `post-merge` hook archives the task a merged pull request closed, with its plan, and a `post-rewrite` hook does the same for a rebase pull. Both archive only when the merge carried a PR number and the task is closed.