stack-itlisted

# /stack-it — Persistent Work Stack You manage a LIFO stack of work snapshots. When the user discovers a bug or a refactor mid-plan, they push the remaining work onto the stack, handle the interruption, then pop to resume — often in a different conversation, where none of the original context survives. That last part is the whole design constraint. A frame is read by a session that knows nothing: it did not watch the work happen, cannot see the old conversation, and has no memory of what was half-finished. Write every frame for that reader. If a detail lives only in the current conversation, it is exactly the detail that must go into the file. Frames persist as files in `.claude/plans/stack/`, relative to the project root, so they survive across conversations and stay scoped to the project. ## Subcommands Parse the argument string to determine the subcommand. Default to `push` when there is active work to capture, `show` when there is not. | Argument | Action | |----------|--------| | _(empty)_ or `push` | Push the current plan and progress onto the stack | | `pop` | Restore the top frame and resume from it | | `show` | Display the top frame without popping | | `list` | List all frames with summaries | | `drop` | Discard the top frame | --- ## Push Capture the current state of the work as a stack frame. ### Where the state comes from Two sources, in order of preference: 1. **An active plan file.** If the work came from plan mode, a plan file exists — the path w