agentsclimarketplace

Resume

Skill pooyagolchian/specforge/plugins/specforge/skills/resume

Spec-driven AI development lifecycle for Claude Code — spec-kit + AI-DLC fused, with hook-enforced human-approval gates. Installable plugin + marketplace.

Install
npx -y skills add pooyagolchian/specforge --skill resume

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

2 things to look at

  • 14 days oldThe repository was created 14 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 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.

What its author says it does

Copied from the file, not written here

Resume the SpecForge lifecycle after a context reset or a break by finding the first unfinished step and continuing. Use when the user wants to pick up where they left off, continue the workflow, or asks "what were we doing". Reads state.md and the active feature's artifacts to determine the next action.

SKILL.md

1.6 KB, 297 tokens by cl100k_base, as published. Nobody here has run it

/specforge:resume — pick up where you left off

Reconstruct context from the on-disk state (which survives context compaction) and continue the lifecycle at the first unfinished step.

Steps

  1. Read specforge/state.md: get the active feature and the stage approval table.
  2. Determine the earliest incomplete step for the active feature, in lifecycle order: constitution → specify → clarify → plan → tasks → analyze → implement.
    • A stage that needs human approval (specify, plan) but is only done (not approved) is the next action → prompt for /specforge:approve <stage>.
    • If implement is in progress, open the active feature's tasks.md and continue at the first unchecked [ ] task.
  3. Briefly re-summarize the feature (from spec.md) so the user has context again.
  4. State the single next action and offer to take it (e.g. "Next: continue implementation at T024 — shall I proceed?").

Guardrails

  • Trust the files, not memory: state.md, tasks.md, and the artifacts are the source of truth.
  • If code edits are needed but the gate is blocked, say so and point to approval / fast-track.
  • Do not restart completed work — resume at the first unchecked item.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.