القائمة
Resume an interrupted iteration by analyzing state.md plus plan.md's task table and suggesting the next safe execution step or escalation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run live continuous co-review or replay persisted reviewer evidence for an iteration.
Run live continuous co-review or replay persisted reviewer evidence for an iteration.
Run live continuous co-review or replay persisted reviewer evidence for an iteration.
Perform a Specrew human-verdict boundary stop on the Claude host. Renders the FULL Rule 46 six-section human re-entry packet AND the verdict options as one Markdown message, with the AskUserQuestion picker disabled so the packet cannot collapse into the picker's short header/option fields. Invoke at EVERY human-judgment boundary stop (specify, clarify, plan, tasks, before-implement, implement, review, retro, feature-closeout, lifecycle-end). Triggers: boundary stop, verdict, approve / redirect / send back, why I stopped, human re-entry packet, gate stop.
{what this skill teaches agents}
Run Specrew's per-lens design workshop and collaborative design-analysis. Use whenever you work the design lenses for a feature: at specify/intake (the lens workshop) and at the design-analysis stop (co-design the architecture), and RE-INVOKE at the start of EACH new lens (architecture, data, ui-ux, security, integration, devops, requirements/NFR, observability, component). Triggers: design, design lens, lens workshop, design-analysis, architecture, trade-offs, co-design, explore options, decompose, or moving from one lens to the next. Tells you to facilitate each lens as a discussion, surface diagrams the human can actually SEE (console ASCII inline; mermaid/html to a file with a clickable file:/// link), co-design components/responsibilities/flows WITH the human instead of handing over finished options, capture the agreements, and which per-lens md to load.
| name | specrew-iteration-resume |
| description | Resume an interrupted iteration by analyzing state.md plus plan.md's task table and suggesting the next safe execution step or escalation. |
| domain | lifecycle-recovery |
| confidence | high |
| source | Specrew governance pillar — iteration resume / recovery helper |
Type: Recovery Skill
Schema: v1
Status: Active recovery method
Resumes interrupted iterations by analyzing state.md plus the authoritative task table in plan.md, then suggests the next execution step or active repair escalation.
| Input | Type | Required | Description |
|---|---|---|---|
| iteration_directory | path | Yes | Path to specs/<feature>/iterations/NNN/ containing state.md and plan.md |
| resume_mode | enum: continue, replan, abort | Yes | How to resume the iteration |
state.md to extract:
plan.md to read the authoritative task table and current task statuses.state.md metadata against the task table:
Tasks Remaining, In Progress, and Updated metadata when possibleplanned tasks as remaining work and in-progress / needs-rework tasks as active workstate.md references unknown tasks or plan-blocked tasksresume_mode:
.squad/config.json with sync-squad-model-overrides.ps1, otherwise resume the current in-progress task or suggest the next incomplete taskstate.md when the iteration is resumable or intentionally being re-planned/aborted| Output | Type | Description |
|---|---|---|
| status | enum: ready, blocked, needs-replan | Resumption readiness |
| last_completed_task | string? | ID of last successfully completed task |
| in_progress_tasks[] | array | Tasks that were started but not finished |
| remaining_tasks[] | array | Tasks not yet started |
| next_suggested_task | string? | Task ID to execute next (null if blocked) |
| next_recovery_action | string? | Escalation step to resume before normal task work |
| repair_escalation | object | Persisted escalation state from state.md |
| blockers[] | array | Issues preventing resumption |
| blockers[].type | enum: dependency, role, resource | Type of blocker |
| blockers[].description | string | What is blocking progress |
| salvageable_tasks[] | array? | Tasks that can be moved to next iteration (if abort mode) |
state.md with repaired execution metadata, resume timestamp, escalation summary, suggested next task, and resume reportstate.md is not found under iteration_directory: infer state from plan.md (all tasks assumed "planned")plan.md is not found under iteration_directory: return error (cannot resume without plan)state.md references unknown tasks or blocked work: report blockers and preserve the existing filepwsh -File .\.specify\extensions\specrew-speckit\scripts\resume-iteration.ps1 `
-IterationDirectory .\specs\001-feature\iterations\000 `
-ResumeMode continue
Expected Output (READY): status: "ready" last_completed_task: "T-003" in_progress_tasks: [] remaining_tasks: ["T-004", "T-005", "T-006"] next_suggested_task: "T-004" blockers: [] salvageable_tasks: null
Expected Output (BLOCKED): status: "blocked" last_completed_task: "T-003" in_progress_tasks: ["T-004"] remaining_tasks: ["T-005", "T-006"] next_suggested_task: null blockers: - type: "dependency" description: "T-004 is blocked waiting for external API access" - type: "role" description: "Reviewer role is unassigned; cannot proceed to review phase" salvageable_tasks: null
Expected Output (ABORT): status: "needs-replan" last_completed_task: "T-002" in_progress_tasks: [] remaining_tasks: ["T-003", "T-004", "T-005"] next_suggested_task: null blockers: - type: "resource" description: "Critical blocker: upstream dependency no longer available" salvageable_tasks: ["T-005", "T-006"]
---
**Implementation Status**: Implemented for FR-019 / Iteration 2.