← ClaudeAtlas

dotmdlisted

Manage this repo's plans, docs, and prompts with the dotmd CLI. Use when the user asks what's on the plate, references a plan/doc/prompt (or a slug under docs/), queues work, or wants to start, transition, or close one. Covers the order of operations (briefing → use → set → archive) and the rules for handling saved prompts.
reowens/dotmd · ★ 1 · Data & Documents · score 77
Install: claude install-skill reowens/dotmd
# dotmd workflow This repo's plans, reference docs, and saved prompts are managed by the **dotmd** CLI (markdown + YAML frontmatter). Always drive them through `dotmd` — never hand-edit frontmatter, never read prompts with the file tools, never commit session-local prompts. The session-start hook prints the live verb sheet and a bounded plan-status vocabulary; if it truncates, use the printed `dotmd statuses list --type plan` fallback. Run `dotmd briefing` any time to refresh live state. **Workflow contract** — the irreducible verbs at a glance; the sections below expand each one. <!-- dotmd:canonical-workflow:start --> - **Orient:** `dotmd briefing` — active / paused / ready work, with ages and next steps. - **Start a plan:** `dotmd use <plan-file>` — marks it `in-session` and prints the plan card. - **Single status verb:** `dotmd set <status> [<file>]` writes the status, validates it against the doc's type, runs lifecycle hooks, fixes refs, and syncs the index. **Never hand-edit a `status:` line.** Add `--note "why"` to record the reason in `## Version History` in the same call. - **Close to match reality:** `archived` (shipped) · `partial` (tail deferred — link the successor) · `active` (more work later) · `awaiting` (needs a human decision) · `blocked` (external arrival you can't speed up). Parking a plan with a known next step? Leave a baton in the same breath — never narrate the next pickup into chat. - **Hand off / save a resume prompt:** `dotmd baton [<slug>] <@<fi