Resume planning

Skill gylove1994/superpowers-deepseek-v4/skills/resume-planning

Use as the strict first step every time the writing-plans SKILL is about to start. Requires the user to select a Done source spec, then scans existing plan-progress files for that spec and offers continue / new based on Done / new based on Abandoned / abandon options.From its SKILL.md

Install

npx -y skills add gylove1994/superpowers-deepseek-v4 --skill resume-planning

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.8 KB, as published. Nobody here has run it

Resume Planning

When to invoke

This SKILL is the first step of every writing-plans invocation. The refactored writing-plans SKILL calls this before doing anything else.

Announce at start: "I'm using the resume-planning SKILL to set up the planning session."

What it does

Force the user to select a Source Spec (mandatory; planning has no meaning without one).
Scan docs/superpowers/brainstorms/*-plan-progress.md.
Bucket files by Status metadata: In Progress, Done, Abandoned. Further split each bucket by whether the file's Source Spec matches the user's selected spec ("same spec" vs "other spec, for cross-borrowing reference only").
Present the menu (see below) and act on the user's choice.

Step 1: Source spec selection

Show:

docs/superpowers/specs/ in Done status (M, most recent 5 shown):
  [s1] <date>-<slug>-design.md
  [s2] ...

Enter the id (e.g. "s1") of the spec for which this planning session is being created, or type a full path.

If the user types a path that does not exist or is not in Done status, ask again. Do not proceed.

Carry the chosen <source_spec_path> into all subsequent steps.

Step 2: Scan and bucket plan-progress files

Read every docs/superpowers/brainstorms/*-plan-progress.md and parse out Status and Source Spec from each.

Bucket as follows:

In Progress
Done — same spec
Done — other spec (cross-borrowing reference only)
Abandoned — same spec
Abandoned — other spec

Step 3: Menu

docs/superpowers/brainstorms/ plan-progress for Source Spec = <chosen path>:

In Progress (N):
  [1] <date>-<slug>-plan-progress.md
      Current Phase: <phase>
      Last Updated: <timestamp>
  [2] ...

Done — same spec (M):
  [d1] <date>-<slug>-plan-progress.md
  ...

Done — other spec, for borrowing reference only (K, most recent 5):
  [d3] <date>-<slug>-plan-progress.md — Source Spec: <other-spec>
  ...

Abandoned — same spec (P):
  [a1] ...

Abandoned — other spec (Q):
  [a3] ...

Please choose:
  A) Continue an In Progress session (recommended; precise recovery via Current Phase) → "<number>"
  B) Start a new session based on a Done                                                → "new based on <id>"
  C) Start a new session based on an Abandoned                                          → "new based on <id>"
  D) Abandon an In Progress session                                                      → "abandon <number>"

Apply the same omission rules as resume-brainstorming (skip absent buckets). If all buckets are empty after omission, bypass the menu and return proceed-with-new-empty along with the source spec path; the writing-plans SKILL then creates a fresh plan-progress file from the template and writes the source-spec metadata into it.

Acting on the user's choice

A — Continue In Progress

Read the chosen file in full.
Return: file path + parsed Current Phase to the writing-plans SKILL.

B — Start new, based on a Done

Read the Done file in full.
Create docs/superpowers/brainstorms/<today>-<slug>-plan-progress.md from the template, set Source Spec: <chosen path> and Based On: <Done filename>.
Inject the Done file's full content as context for the writing-plans SKILL to begin draft writing from.
Return: new file path, Current Phase: draft_writing, plus the prior file content as context.

C — Start new, based on an Abandoned

Same as B, surfacing the abandonment rationale (if present) as additional context.

D — Abandon an In Progress

Same procedure as resume-brainstorming option D: set Status: Abandoned, append an Abandonment section, commit, re-run this SKILL.

Current Phase precise recovery (for option A)

Current Phase	Resume behaviour
`draft_writing`	Read the source spec and any prior writing notes. Continue from the draft on disk.
`review_round_N`	Re-dispatch round N's reviewers (draft is in the working directory, unchanged because mid-loop commits never happen).
`awaiting_user_decision`	Re-present the open `I<n>` block(s) to the user.
`finalizing`	Re-present the converged plan for final sign-off.

What this SKILL does NOT do

It does not modify the chosen file (except option D's abandonment edit).
It does not start the writing-plans flow itself.
It does not commit anything except in option D.
It does not auto-decide; the user always picks from the menu (and always picks the source spec first).

File referenced

./templates/plan-progress-template.md — the verbatim template used when creating new files.