draft-park

draft-park — human-in-the-loop drafts via macOS Notes

Renamed from draft-hold on 2026-08-12. Invoke as /notes-commander:draft-park; there is no draft-hold alias. Evolution-log entries dated before the rename keep the old name — that is the accurate historical record, not drift.

Self-Evolving skill — if macOS Notes/Stickies behavior drifts from what's below, fix this SKILL.md and the shared engine scripts/lib/notes-core.ts (+ a case in notes-core.test.ts); see the Post-Execution Reflection at the bottom.

When you compose something a human should confirm or edit before it goes out (a message to a real person, an announcement, a commit body), don't keep it only in chat — park it in macOS Notes so the operator can edit it on any device, then read it back and act on the edited version.

Resolve the entrypoint first — $CLAUDE_PLUGIN_ROOT is NOT a shell variable and expands to empty here (it exists only inside plugin manifests and hook/MCP subprocesses; see the $CLAUDE_PLUGIN_ROOT invariant in the plugin CLAUDE.md). Never glob the version cache either — it retains orphaned versions. Use the resolver:

DP="$(cc-plugin-root notes-commander)/skills/draft-park/draft-park.sh"

draft-park.sh is a thin shim that execs the Bun/TypeScript engine scripts/draft-park.ts, built on the plugin's shared notes-core engine (which also powers notes-inventory/notes-export/notes-organize).

Formatting is handled in code — just write naturally

The engine (formatter in scripts/lib/notes-core.ts, unit-tested in notes-core.test.ts) normalizes your input into Notes HTML, so you never hand-manage line breaks:

• Prose reflows. Consecutive non-blank lines join into ONE paragraph that Notes soft-wraps to the reader's screen. Accidental hard-wrapping (text pre-wrapped at ~80/100 cols) is corrected automatically — it can no longer become a permanent mid-sentence break. Blank lines are the only breaks that matter.
• A blank line = a new paragraph/section. That is the one authored break.
• Bullet lists become NATIVE Notes lists, and they nest. Lines starting -, *, +, •, · are emitted as real <ul>/<li>, so Notes draws its own bullet glyph and indents sub-items natively — indent a child by two spaces (a tab counts as one unit) and it nests. The marker is consumed; do not expect to see your own -. Numbered and lettered markers (1., 2), a.) deliberately keep the literal-marker form, because Notes' own numbered list renumbers from 1 and would silently rewrite an author's 2) as 1.. A wrapped continuation line (indented, no marker) still joins back to its item, and its own indentation does not move the item.
• Markdown emphasis becomes REAL RICH TEXT — do not hand-strip it. Notes is a rich-text editor, so **bold** → bold, *italic* / _italic_ → italic, `code` → monospaced, ~~strike~~ → struck, and #/##/### headings → a bold line with the markers consumed. Write in the house markdown style and it arrives formatted. Two deliberate exceptions keep technical prose safe: an identifier can never open or close emphasis (analytics.model_predictions and nan_policy stays literal, as does 2*3*4), and anything inside backticks or a fence keeps its markers verbatim.
• Verbatim / columnar / code blocks — wrap them in a ``` fence. Every line inside is preserved exactly and rendered monospace with spaces held (via  ), so columns and IDs line up in the Notes UI. (Note: get --body-only returns the sendable plain text and collapses inter-column runs to single spaces; if exact alignment must survive to the recipient, send an attachment/screenshot.)