القائمة
Recover active change and next action from artifacts. Use on fresh session with existing work.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Optional product go/no-go on a framed spec. Use when product direction needs review before planning.
Optional engineering go/no-go on a plan. Use when execution safety needs review before implementation.
Implement approved plan slices. Use as the execute-stage entry point.
Bound and de-risk a request into SPEC.md. Use when the objective is clear but scope needs constraining.
Sharpen a vague idea into a bounded objective. Use before framing when scope is undefined.
Build project truth from repo evidence. Use when steering is missing or stale.
| name | auto-resume |
| description | Recover active change and next action from artifacts. Use on fresh session with existing work. |
| metadata | {"stage":"resume"} |
Session recovery. Rebuilds context from durable artifacts, not memory or guessing.
First action: run node .agent/.automaton/scripts/get-context.mjs from the project root.
auto-resume rebuilds context from durable artifacts, not from the user's description or the agent's training data. It does not modify artifacts, advance the stage, or start new work. It loads canonical artifacts in dependency order (spec first, then design, then plan) and reports what it found, what was blocked, and what comes next.
Loading discipline: start with artifacts needed for the current stage. Read project files when understanding the codebase helps rebuild accurate context for the next action. Read .agent/.automaton/references/CONTEXT-BUDGET.md when wider reads threaten context pressure.
Before producing the recovery summary:
references/quality.md when the summary becomes narrative recap.Read .agent/.automaton/references/ARTIFACT-LIFECYCLE.md for recovery order, stale-pointer handling, and stage handoffs.
Halt and report when:
.agent/ does not exist or current.json is missing.Recommend auto-onboard and stop. Do not attempt recovery without a state file.
If work is complete or absent, read .agent/steering/ROADMAP.md only to surface pending phases as context.
Check that canonical_spec, canonical_design, and canonical_plan resolve when present. If any pointer is stale, report it plainly; recommend auto-onboard for missing steering, auto-frame for missing SPEC.md, or auto-plan for missing PLAN.md.
Treat current.json as the only source for active change, stage, and canonical artifact pointers. Load artifacts in dependency order and stop at the current stage; read references/artifact-order.md for the full stage table.
If current.json contains product_review or engineering_review, read the corresponding ## Review: sections from canonical artifacts and include them in the resume summary.
Produce a concise summary under 200 tokens:
**Active change:** [name]
**Stage:** [frame|plan|execute|verify|verified|resume]
**Artifacts loaded:** [list]
**What was done:** [1-2 sentences]
**What was blocked:** [1-2 sentences, or "nothing"]
**What comes next:** [specific next action, or "none - change complete"]
**Review verdicts:** [product: X, engineering: Y, or "none"]
**Missing state:** [list or "none"]
**Roadmap:** [N pending / M total, or "not tracked"]
The goal is orientation, not transcription.
Use references/recovery-scenarios.md for the full routing table. The invariant: recommend the next lifecycle skill only when recovered state is incomplete or blocked. For verified completion, report no next lifecycle skill; if ROADMAP.md has pending items, surface them as optional future work, not an automatic auto-office-hours handoff.
.agent/.automaton/state/current.json is read-only for auto-resume; stale pointers are reported, not silently repairedNext: <skill>; none when the active change is verified complete. The user picks the direction.auto-onboard.auto-office-hours handoff.