القائمة
Restore session context from the task checklist — add 'continue' to also resume execution from the first non-closed item
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Execute a planned multi-phase task — resume from /plan's committed artifacts and run each phase red→green→refactor inline in the main session under hook enforcement and script gates. Generation stays in one hot context; agents are spawned only to verify (spikes already done, review lanes, refuters, seam, provenance, drive). One final user gate over the whole task diff — for large tasks (15+ files), after /plan.
Archive an agreed design as a task specification — requirements with stable R-ids, a ratified tests.manifest.json (contract rows, decision rows with enforcement pointers, touch map, spike list), a slimmed mechanics doc for the prose residue, taste decisions drafted into meme, one tandem commit
Turn a ratified tests.manifest.json into an executable plan — scaffold phases, fill decision slots inline, run environment spikes as verification probes, lint, delta-review, bake baselines, and land one plan commit. The generation half of the build pipeline; everything it produces is a file, so /build resumes from disk. Run after /spec, before /build, for large multi-phase tasks.
Code review via risk-routed judgment lanes — static tools first, then only the lanes the diff's surface warrants, blocker findings refuter-verified and fixed green-to-green
Dialectic architecture and design debate — argue until consensus, close every ambiguity, and land the agreement as falsifiable candidate rows (scenarios, decisions, spikes) ready for /spec to ratify
Close out a task — results generated from checklist and verification data plus a hand-written narrative delta, the amendment log drafted into meme, backlog reconciled, living docs swept for staleness
| name | restore |
| description | Restore session context from the task checklist — add 'continue' to also resume execution from the first non-closed item |
| argument-hint | Path to task — or 'continue' to resume execution (e.g., docs/tasks/043-harness-redesign continue) |
Resume long-running work from its data plane. The checklist is the state; restoring is reading it, not reconstructing history. Load context only for incomplete work — completed phases need no re-reading.
$ARGUMENTS carries an optional task path (directory containing requirements.md) and an optional continue flag. No path → auto-detect: find . -name "requirements.md" -path "*/docs/*" -mtime -14 | head -5 plus git log --oneline -10 for recent activity.
<task-path>/plan/checklist.json — the resume point is the first phase not closed, first item not done. No checklist → the task predates the manifest pipeline or never reached /build planning; fall back to reading requirements.md and reporting that state.closed whose commit is absent from git log is stale state — surface it as the resume point, never as completed. Receipts in the state dir (${XDG_STATE_HOME:-$HOME/.local/state}/claude-build/<repo>/<task>/receipts.jsonl) outrank checklist claims; git status --short shows any in-flight working-tree state.requirements.md (Done-When + Deferred slices) and tests.manifest.json amendment entries — pending proposed rows are open user decisions and must be surfaced.Do not read plan payloads for closed phases, results of completed work, or full historical diffs.
## Session Resumed
- Closed: [phases with commits confirmed in git log]
- In flight: [first non-closed phase, its last leg per receipts, uncommitted files]
- Open decisions: [proposed amendment rows awaiting ratification]
- Blockers: [open blocker findings, held dependents]
- Next: [the concrete next action]
Without continue: STOP HERE.
Re-enter /build at the point the state names: an unratified amendment → surface it first; an in-flight phase with a red receipt but no close → resume that phase in-session from the checklist (green leg onward); a closed-but-uncommitted phase → run the close gate and commit; otherwise launch the next ready phase per /build Step 1.