القائمة
Use when the user wants to temporarily disable Athena workflow routing and gates — pauses all auto-triggers and skill checks until /athena-resume is invoked
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | athena-pause |
| description | Use when the user wants to temporarily disable Athena workflow routing and gates — pauses all auto-triggers and skill checks until /athena-resume is invoked |
Temporarily disables all Athena workflow enforcement. Hooks stop firing, athena-init stops routing, gates stop blocking. Use when the user needs to do quick ad-hoc work without ceremony.
Ask once:
"Pausing Athena — skill routing, verification gates, and auto-triggers will be disabled. Resume with
/athena-resume. Pause now?"
If the user confirms (or invoked /athena-pause directly), proceed.
Write to .athena-state.json in the project root:
{
"paused": true,
"pausedAt": "2025-01-15T10:30:00Z",
"pausedBy": "user"
}
Preserve any existing fields in the state file — only set paused, pausedAt, and pausedBy.
Athena PAUSED
══════════════
Disabled: skill routing, verification gates, auto-trigger hooks
Resume: /athena-resume
/athena-verify, it still works.athena-state.json continues tracking (so resume knows where you left off)If the user asks to reset Athena state (e.g., "reset athena", "clear athena state", "start fresh"), or if state appears wedged (stuck in a phase that no longer applies):
.athena-state.pre-reset.json.athena-state.json with only {} (or { "paused": true } if also pausing).athena-edit-burst.json if it existsAthena State RESET
════════════════════
Previous state backed up to .athena-state.pre-reset.json
Pipeline: cleared
Phase: none
Ready for: /athena-plan or /athena-brainstorm
/athena-resume in the confirmationUse 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