Resume
Skill pooyagolchian/specforge/plugins/specforge/skills/resume
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.From its SKILL.md
npx -y skills add pooyagolchian/specforge --skill resumeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 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.
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
- Read
specforge/state.md: get theactivefeature and the stage approval table. - 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 onlydone(notapproved) is the next action → prompt for/specforge:approve <stage>. - If
implementis in progress, open the active feature'stasks.mdand continue at the first unchecked[ ]task.
- A stage that needs human approval (
- Briefly re-summarize the feature (from
spec.md) so the user has context again. - 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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most hr recruiting skills give in 297 tokens
Counted across 356 of the 357 authors here whose files we hold, read 2026-08-07
- Quantify achievements with specific metricsin 14 of 356, across 6 files
- Keep the resume under two pagesin 14 of 356, across 6 files
- Request the full job description if not providedin 12 of 356, across 4 files
- Extract keywords and prioritize job requirementsin 12 of 356, across 4 files
- Stop and ask for clarification if required inputs are missingin 12 of 356, across 5 files
- Map candidate experience to job requirementsin 11 of 356, across 3 files
- Ask if the user wants adjustmentsin 11 of 356, across 3 files
- Provide strengths and gap analysis after the resumein 10 of 356, across 2 files
- Request candidate background details if not providedin 10 of 356, across 2 files
- Format experience bullets as action verb plus resultin 10 of 356, across 2 files
- Ask for missing inputs before startingin 10 of 356, across 9 files
- Use exact job description terminologyin 9 of 356, across 1 file
Said here and by no other author read
- identify the active feature
- find the earliest incomplete workflow step
- prompt for stage approval when required
- resume implementation at the first unchecked task
- summarize the feature for the user
- state the next action and offer to take it
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.