# Plan:resume

> Resume working on an in-progress implementation plan. Finds incomplete plans and provides context to continue.

- Skill: `majiayu000/plan-resume` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/plan-resume`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/plan-resume/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/plan-resume

---


# Resume Skill

Find and resume work on an in-progress implementation plan.

## Process

1. **Scan for in-progress plans:**
   - Look for `plans/*/task-list.md` files (exclude `plans/archive/`)
   - A plan is "in-progress" if it has unchecked task boxes: `- [ ]`

2. **For each in-progress plan found, gather context:**
   - Read `.plan-state.json` if it exists:
     - `created_at` - when the plan was created
     - `updated_at` - last state update
     - `planning_agent_id` - agent ID from original planning session (for resumption)
     - `current_task` - task that was in progress
     - `last_session_notes` - notes from previous session
     - `progress.completed` / `progress.total` - task counts
   - If no state file, calculate progress by counting checkboxes in task-list.md:
     - `- [x]` = completed
     - `- [ ]` = incomplete
   - Extract the first 3-5 uncompleted task descriptions

3. **Handle different scenarios:**

   **No plans found:**
   ```
   No in-progress plans found in `plans/`.

   To create a new plan, use `/plan:create <feature description>`.
   ```

   **One plan found:**
   Display the resume output (see format below).

   **Multiple plans found:**
   List all plans and ask user to choose:
   ```
   Found multiple in-progress plans:

   1. `plans/0006-rust-parser/` - 3/12 tasks (25%)
   2. `plans/0007-output-formats/` - 0/8 tasks (0%)

   Which plan would you like to resume? Enter the number or plan name.
   ```
   Then display resume output for the chosen plan.

4. **Display resume output:**
   ```
   **Resuming plan:** `plans/NNNN-feature-name/`

   **Progress:** N/M tasks complete (X%)
   **Created:** YYYY-MM-DD HH:MM UTC
   **Last session:** YYYY-MM-DD HH:MM UTC (or "No previous session" if no state file)
   **Planning agent:** `{agentId}` (or omit if not in state file)
   **Last notes:** "Notes from previous session" (or omit if null)

   **Next tasks:**
   - [ ] **2.1** First incomplete task
   - [ ] **2.2** Second incomplete task
   - [ ] **2.3** Third incomplete task
   ```

5. **Begin implementing the plan using strict TDD:**
   - Read the task file in `tasks/` for each task before starting it
   - For each task, follow the TDD cycle:
     1. **🔴 Red:** Write the failing test(s) specified in the task file. Run them to confirm they fail for the expected reason. Do not write any implementation code.
     2. **🟢 Green:** Write the minimum code to make the test(s) pass. Run tests to confirm.
     3. **🔵 Refactor:** Clean up the code while keeping tests green. Commit after refactoring.
   - Mark tasks complete in task-list.md after the full Red/Green/Refactor cycle
   - Update .plan-state.json with current_task and progress.completed
   - **When completing a phase:** Create a commit with message format:
     `feat(plan-NNNN): Phase N - <phase description>`
   - Add each commit SHA to the `commits` array in .plan-state.json

6. **Record findings during implementation:**
   - Create a `findings/` subdirectory in the active plan directory
   - Write findings as individual markdown files with descriptive names
   - Record any of the following as they arise:
     - **Discoveries:** Unexpected behavior, undocumented assumptions, or new understanding of the codebase
     - **Diversions:** Where the implementation diverged from the plan and why
     - **Plan errors:** Things the plan got wrong — incorrect assumptions, missing steps, wrong approach
     - **Important notes:** Context that future sessions or plans should know about
     - **TODOs:** Work identified but deferred — cleanup, optimization, follow-up features
     - **Cleanup items:** Technical debt introduced or discovered during implementation
   - Use this format for finding files:
     ```markdown
     # Finding: Short Title

     **Type:** discovery | diversion | plan-error | note | todo | cleanup
     **Task:** 2.1 (which task surfaced this)
     **Date:** YYYY-MM-DD

     ## Details
     [What was found/changed/wrong]

     ## Impact
     [How this affects the current plan or future work]

     ## Action Items
     - [ ] Concrete next step (if any)
     ```
   - These findings will be used to create issues and provide feedback to research

## Example Outputs

### Single Plan Found

---

**Resuming plan:** `plans/0008-rust-parser/`

**Progress:** 3/12 tasks complete (25%)
**Created:** 2026-01-22 14:30 UTC
**Last session:** 2026-01-23 16:45 UTC
**Planning agent:** `a1b2c3d4-e5f6-7890-abcd-ef1234567890`
**Last notes:** "Completed data model, starting parser implementation"

**Next tasks:**
- [ ] **2.1** Implement panic message regex
- [ ] **2.2** Parse backtrace frame format
- [ ] **2.3** Handle thread panic variants

---

### Multiple Plans Found

---

Found multiple in-progress plans:

1. `plans/0006-rust-parser/` - 3/12 tasks (25%)
2. `plans/0007-output-formats/` - 0/8 tasks (0%)

Which plan would you like to resume? Enter the number or plan name.

---

### No Plans Found

---

No in-progress plans found in `plans/`.

All plans are either completed (in `plans/archive/`) or none exist yet.

To create a new plan, use `/plan:create <feature description>`.

---