القائمة
Reconstruct the exact pipeline position from disk, load the frontier spec in full, list failed approaches not to retry, and present the next action. Read-only, any time.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | Resume |
| description | Reconstruct the exact pipeline position from disk, load the frontier spec in full, list failed approaches not to retry, and present the next action. Read-only, any time. |
| argument-hint | [feature-name] |
The "I just got here — what's happening?" command. Reconstructs the pipeline position from disk, loads only the active group's state and the frontier (next) spec in full, lists failed approaches not to retry, and presents the next action. Read-only — never writes approval records.
approvals/master.json + the one active group-{N}.json (max two approval files).genesis/project-state.md (active feature + mode)units.json (lowfield)tried.json (failed approaches), filtered to the frontier specjournal/ (for absence sizing)git status (uncommitted work)project-state.md; if several, ask).RESUME: <feature>
Feature phase: <status> (<phases> approved)
Groups: N/total complete
Active group: N (<title>) Active spec: <spec-id> (<title>)
Status: clean|partial — <detail>
Tried: N approaches logged (<summary>)
Next: <next pipeline action>
Brownfield adds a scope reminder (files in scope) and regression notes. Lowfield adds a unit-progress summary and the next unit action.
- "resume"
- "where did I leave off"
- "what's next"
- "catch me up"
The drift check. Compare what was built against the design doc and master spec. Sets the Double Gate — A3 cannot start until A1 is at zero findings.
Mechanical FR/AC compliance. Walk every functional requirement and acceptance criterion and render a binary Pass/Fail with evidence. No judgment about quality, direction, or architecture.
Code/content quality. Dead code, hardcoded values, leftover TODOs, weak error handling, security holes, performance traps, standards violations. Enforces the Double Gate — blocks until A1 is at zero findings.
Vision-gap analysis. Compared to the perfect-world North Star, what is missing, drifting, or underbuilt — and what to add or change now to close the gap. Not a passive alignment scorecard.
Research the world. Real web research to find what the best teams do for every technology and pattern in the build, then implement superior approaches now (not later). The only lens that brings outside knowledge.
The boundary ritual — review what just landed, record an approval, journal it, and advance the phase. The ONLY step that writes approvals, and it does NO git.