メニュー
Use when the user wants to re-enable Athena workflow routing and gates after a /athena-pause — restores all auto-triggers and skill checks
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | athena-resume |
| description | Use when the user wants to re-enable Athena workflow routing and gates after a /athena-pause — restores all auto-triggers and skill checks |
Re-enables Athena workflow enforcement after a pause. All hooks, routing, and gates return to normal.
Read .athena-state.json:
paused !== true: "Athena is not paused — nothing to resume."paused === true: proceedUpdate .athena-state.json:
paused to falsepausedAt and pausedByCheck the state file for pipeline context and report:
Athena RESUMED
═══════════════
Was paused since: [timestamp]
Pipeline state: [phase from state file, or "no active pipeline"]
Last verification: [timestamp and result, or "none recorded"]
All routing, gates, and auto-triggers are active.
Based on the pipeline state:
phase === "planned": "You have an unexecuted plan. Run /athena-build to start."phase === "build-stuck": "Build was stuck before pause. Run /athena-debug to investigate."phase === "build-complete": "Build completed before pause. Run /athena-review or /athena-ship."After resuming, check if the state looks sane:
phase is set but the plan file doesn't exist → WARN: "Pipeline references a plan that no longer exists. Consider /athena-pause with a state reset."wave.current > wave.total → state is corrupt. Reset to {} and note: "State was inconsistent — reset to clean state."lastVerification.timestamp is more than 24 hours old → INFO: "Last verification was over 24 hours ago. Consider re-verifying with /athena-verify."/athena-pause with a state reset to start freshUse before any creative work, new features, architecture changes, or behavior modifications — explores intent, constraints, and design before implementation begins
Execute an implementation plan using the coordinator pattern — per task, dispatch implementer → spec-reviewer → code-quality-reviewer; per wave, synthesize and verify. Parallel where independent, sequential where dependent. Use when you have a plan ready to execute.
Use during brainstorming when visual content would help — mockups, wireframes, layout comparisons, architecture diagrams. Zero-dependency, no server required.
Systematic debugging with hypothesis tracking, evidence collection, and checkpoint management. Use when encountering any bug, test failure, or unexpected behavior — diagnoses before fixing.
Use when implementation is complete and you need to merge, create a PR, keep, or discard a branch — handles integration and cleanup after development work
Use when creating new Athena skills, editing existing skills, or building skills for any Claude Code plugin — guides skill authoring with TDD validation