Captures ideas and rich conversation context for later. Creates a backlog entry linked to a detailed conversation summary in .lo/park/. Use when user says "park this", "save this for later", "park", "remember this idea", or "/lo:park". Not for planning or execution — use /lo:plan to design, /lo:work to build.
Captures ideas and conversation context for later. When you've been discussing something with Claude and want to save the thinking without committing to planning or building, park it.
/lo:park/lo:plan/lo:plan (creates backlog entry + plans in one motion)/lo:work (creates backlog entry + executes)/lo:ship.lo/ directory must exist. If missing, tell user to run /lo:setup first.last_feature and last_task from BACKLOG.md frontmatter for ID allocation.Detect mode from arguments:
/lo:park (no args) → Mode 1: Capture from Conversation/lo:park feature "name" → Mode 2: Quick Park (backlog entry only)/lo:park task "name" → Mode 2: Quick Park (backlog entry only)This is the primary mode. The user has been discussing something and wants to preserve the thinking.
Suggest a name based on the conversation topic:
What should I call this?
1. [suggested name based on conversation]
2. Something else
Classify as feature (f{NNN}) or task (t{NNN}) based on scope. Features are bigger and need design. Tasks are smaller, just-do-it items. If scope is ambiguous, ask:
Is this a feature (bigger, needs design) or a task (smaller, just do it)?
Step 2: Generate the conversation capture.
Read the conversation context and produce a rich, near-verbatim summary that preserves the thinking. This is NOT a structured extraction — it reads like meeting notes that capture the actual flow of ideas.
Include all of these:
The capture should be long enough that future-you can read it and be immediately back in the headspace. Err on the side of too much context rather than too little.
Format the capture file per references/park-format.md:
# <id> — <name>
parked: <YYYY-MM-DD>
<Rich narrative capture. Multiple paragraphs.
Preserves the flow of thinking, not just the conclusions.>
Step 3: Present for review.
Show the complete capture to the user:
Here's what I captured. Review and approve, or tell me what to change:
---
[full capture content]
---
Save this? (yes / edit / redo)
HARD GATE: Do not write any files until the user approves. If the user says "edit" or "redo", ask what to change, regenerate, and re-present. Repeat until approved.
Step 4: Persist.
After the user approves:
# Read the counter from frontmatter
grep 'last_feature:' .lo/BACKLOG.md # → last_feature: 9
# Next feature ID = last_feature + 1 → f010
.lo/park/ directory if it doesn't exist:mkdir -p .lo/park
# Path: .lo/park/<id>-<slug>.md
# Example: .lo/park/f010-image-gen.md
# f010 — Image Generation for MDX Pipeline