القائمة
Use when [specific trigger, symptom, user request, or workflow state]
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when a plan or spec splits into many independently-mergeable units — a codebase-wide migration, rename, or repeated pattern change — and the user wants them implemented in parallel as separate PRs rather than one sequential pass. The fan-out alternative to afk:implement.
Use when the user says "grill me", asks to stress-test a plan, wants to be interviewed or asked the questions needed before building, offers a vague feature idea, or wants grounded planning before non-trivial implementation
Use when the user asks to run the whole AFK flow, ship a feature, take work from idea or plan to verified evidence, resume an AFK workflow, or make a final ship/no-ship call across planning, implementation, cleanup, and QA
Use when a task needs to read or write the persistent brain/ vault — adding a principle, codebase gotcha, or note, or grounding work in existing memory; triggers include "add to brain", "remember this in the brain", or any direct brain/ edit.
Use when the user asks for help, afk help, what to do next, where am I, which AFK skill to use, AFK workflow orientation, or a broad catalog explanation
Use when the agent is about to implement, edit code, execute a plan, fix a bug, build a feature, or make repo changes, especially when task complexity or orchestration needs are unclear. Do not start editing code, writing tests, or running build or test commands directly — load this skill first to triage and route.
| name | skill-name |
| description | Use when [specific trigger, symptom, user request, or workflow state] |
One or two sentences explaining the skill's purpose and core principle. State the invariant this skill protects.
Use this skill when:
Do not use this skill for:
Write steps as commands to the agent. If a step depends on another file, name that file and say exactly when to open it.
STOP and ask the user when:
Do not ask about facts that can be discovered by reading the repo.
| Thought | Reality |
|---|---|
| "[Tempting shortcut]" | [Why it fails and what to do instead] |
| "[Another predictable rationalization]" | [Correct behavior] |
Return this shape:
[Expected final response, artifact, or report format]
If the skill produces a file, name the path pattern and the handoff skill or next workflow step.
related-skill-name - when this skill should defer to it