memolisted

# Memo Park a stray idea now so it isn't lost — without derailing the current task — or review the backlog and pick something up. A memo is lighter than a GitHub issue: a half-formed thought worth keeping, not a tracked unit of work. The backlog lives in `.claude/memos/`, one file per memo, committed with the project. Open items resurface on their own at session start, at task completion, and during `/commit`. ## Context - Repo root: !`git rev-parse --show-toplevel 2>/dev/null || pwd` - Open memos: !`python ~/.claude/skills/memo/memos.py count` ## Arguments `$ARGUMENTS` holds the memo text. It may be empty. ## Storage One memo is one file, so a memo is as long as the idea needs: ``` <Repo root>/.claude/memos/<slug>.md an open memo <Repo root>/.claude/memos/done/<date>-<slug>.md one that has been addressed ``` Open versus done is **which directory the file sits in** — there is no status marker to read or flip. Each file is a frontmatter block carrying `created:` and optionally `platform:`, an `# H1` title, and an optional body: ```markdown --- created: 2026-09-12 05:17:22 platform: windows --- # Improve memos by storing in separate files Body prose, as long as it needs to be. ``` The `memos.py` helper owns the timestamp, the slug, the title derivation and the rendered listing — you hand-format none of them. An open memo's frontmatter carries its sort key rather than its filename, so adding a future ordering (priority, area) is a new field inste