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 one file, `.claude/memos.md`, 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` - Now: !`date '+%Y-%m-%d %H:%M %Z'` - Open memos: !`python ~/.claude/skills/memo/memos.py count` ## Arguments `$ARGUMENTS` holds the memo text. It may be empty. ## Process The memo file is `<Repo root>/.claude/memos.md` — a Markdown checklist, one line per entry, newest at the bottom: `- [ ] <YYYY-MM-DD HH:MM> — <idea>` open (local time, 24-hour), `- [x] …` addressed. The `memos.py` helper owns the timestamp and the rendered, aligned listing (numbered, newest-first, wrapped so each memo's text lines up under its first line) — you hand-format neither. ### If `$ARGUMENTS` is non-empty — record a memo 1. Run `python ~/.claude/skills/memo/memos.py add "<the idea, lightly cleaned up>"`. The helper creates the file (and `.claude/`) if needed, stamps the local time, appends the entry, and prints the new counts. Preserve the user's intent and scope — don't expand a one-liner into a spec. 2. Confirm in a single line with the new open count (e.g. "Memo'd — 3 open."). **Do not** start working on the idea