/SKILL.md
Capture unfinished work, list parked items, or resume parked work. Use when the user says "park this", "save remaining tasks", "handoff", "what's parked", "resume parked work", "park done", "what's left to do", "save progress before clearing", or invokes /park.
npx skillsauth add liamlin/claude-skill-park parkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Persist structured parked files so any future agent (in any session or worktree) can discover and resume work.
Inspect the subcommand argument and run the matching flow:
| Argument | Flow |
|---|---|
| (none) | Park — infer from context, draft, confirm, write |
| "quoted text" or any text that isn't list/resume/done | Park — use text as title |
| list | List — show all parked items |
| resume | Resume — pick an item, create tasks, mark in-progress |
| done or done <slug> | Done — mark a parked item completed |
This is often the last action before the user clears the session. Be aggressive about inferring — do not ask open-ended questions. One confirmation round max.
Run in parallel: git log --oneline -20, git diff --stat HEAD, git branch --show-current
Also:
parked_*.md files to avoid duplicates.claude/plans/*.md for recently modified files)Using the gathered context + conversation history, draft a complete parked file. If the user provided a summary string, use it as the title. Otherwise, infer a title from the work done.
Critical — capture things that won't survive context clear:
Present the draft to the user. If they say "yes", "looks good", "lgtm", or similar — write immediately. If they give corrections, apply and write. One round only.
Location: The project's memory directory (find it by looking for MEMORY.md in the .claude/projects/ tree).
Filename: parked_<slug>_<YYYYMMDD>.md where <slug> is a kebab-case version of the title.
If a file with a matching slug already exists (ignoring the date suffix), update it by default. Create a new one only if the user explicitly requests it.
File format:
---
name: <descriptive title>
description: <one-line summary — will appear in MEMORY.md index>
type: project
status: parked
parked_at: <ISO 8601 timestamp, e.g. 2026-04-03T16:30:00+08:00>
branch: <git branch name>
---
## Completed
- <commit hash> — <commit message>
- Uncommitted: <summary of unstaged/staged changes, if any>
## Remaining
Priority order:
1. **<Item title>** — <what needs to be done>
- Depends on: <dependency, if any>
2. **<Item title>** — <description>
## Key Decisions
- **<Decision>**: <rationale — why this choice was made>
## Pickup Instructions
1. **Read first**: <2-3 most important files for context, with paths>
2. **Run first**: <commands to verify current state, e.g. `pnpm typecheck`, `pnpm test`>
3. **Start with**: <which Remaining item to tackle first and why>
Find MEMORY.md in the same directory. Append one line:
- [parked_<slug>_<date>.md](parked_<slug>_<date>.md) — [PARKED] <summary>
The [PARKED] tag makes items scannable.
Print a brief summary: title, remaining item count, file path. The user can now safely clear the session.
parked_*.md in the project memory directoryname, status, parked_at, branch## Remaining)Parked Work:
1. [parked] shop-api-timezone (2026-04-03, main) — 3 items remaining
2. [in-progress] booking-refactor (2026-04-01, feat/booking) — 5 items remaining
3. [done] queue-fix (2026-03-28, main)
If no parked_*.md files exist, print: "Nothing parked."
status: parked onlystatus: parked to status: in-progress[PARKED] to [IN-PROGRESS] on the matching lineThe tasks are now queued. The agent works through them after finishing current work.
/park done shop-api-timezone), find the matching parked_*.md file by partial slug matchstatus to completed[PARKED] or [IN-PROGRESS] to [DONE] on the matching linedata-ai
Capture unfinished work, list parked items, or resume parked work. Use when the user says "park this", "save remaining tasks", "handoff", "what's parked", "resume parked work", "park done", "what's left to do", "save progress before clearing", or invokes /park.
data-ai
Example TaskFlow authoring pattern for inbox triage. Use when messages need different treatment based on intent, with some routes notifying immediately, some waiting on outside answers, and others rolling into a later summary.
data-ai
Example TaskFlow authoring pattern for inbox triage. Use when messages need different treatment based on intent, with some routes notifying immediately, some waiting on outside answers, and others rolling into a later summary.
data-ai
OpenProse VM skill pack. Activate on any `prose` command, .prose files, or OpenProse mentions; orchestrates multi-agent workflows.