القائمة
AFK (Away From Keyboard) mode - enable tiered modes, check status, review sessions. Use /afk [operation] where operation is full|plan|research|monitor|off|status|review
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | afk |
| description | AFK (Away From Keyboard) mode - enable tiered modes, check status, review sessions. Use /afk [operation] where operation is full|plan|research|monitor|off|status|review |
| allowed-tools | Read, Bash |
Manage AFK (Away From Keyboard) mode with tiered tool access and session tracking.
Parse $ARGUMENTS to determine the operation:
| First Word | Operation | Description |
|---|---|---|
full | enable.md | No tools allowed |
plan | enable.md | Read-only tools (Read, Glob, Grep) |
research | enable.md | Read + web (WebFetch, WebSearch) |
monitor | enable.md | Read + Bash |
off | off.md | Disable AFK mode |
status | status.md | Show current status |
review | review.md | Review planning session |
| (empty/other) | enable.md | Default to full mode |
/afk → full mode, default message
/afk full "In a meeting" → full mode, custom message
/afk plan "Explore codebase" → plan mode (read-only)
/afk research → research mode (read + web)
/afk off → disable
/afk status → check status
/afk review → review current/last session
/afk review 20240115_103000 → review specific session
All state operations use the script at scripts/state.sh:
"${CLAUDE_PLUGIN_ROOT}/skills/afk/scripts/state.sh" <command> [args]
Commands: enable, disable, is-enabled, get-state, get-mode, get-message, get-allowed, is-allowed, get-plan-path, get-log-path
Unified specification refinement plugin. Single entry point for all spec operations: greenfield architecture pipelines (principles → design → stack → spec → plan), feature spec creation in existing systems, iterative convergence loops, quality reviews, drift detection, finalization, ticket decomposition, traceable updates, and lifecycle archival. Detects pipeline state from existing artifact frontmatter and routes intelligently. Use whenever you need to create, refine, validate, or evolve a technical specification.
Core reference for EARS requirement patterns, Given/When/Then acceptance criteria, RFC 2119 language, requirement ID conventions, and specification quality checklists. Background knowledge for the spec-writer agent. Preloaded by spec-writer via the skills frontmatter field; not user-invocable.