القائمة
Use before building anything non-trivial — new features, architectural changes, multi-file modifications. Explores intent, requirements, and design before implementation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Orient in project state before starting work
Review open issues and PRs across the workspace to decide what needs action
Examine evidence (files, logs, code, output) against user instructions and baseline quality factors. Audit only, no fixes.
Use when executing an implementation plan. Builds in TDD cycles with disciplined commits — one commit per plan step, no unrelated files swept in.
Use when diagnosing bugs, test failures, or unexpected behavior. Requires hypotheses before fixes — no jumping to solutions.
Deploy one or more services end-to-end with health verification
| name | brainstorm |
| description | Use before building anything non-trivial — new features, architectural changes, multi-file modifications. Explores intent, requirements, and design before implementation. |
Go from a rough idea to a concrete design through conversation. Explore the problem space before converging on a solution.
/ground yourself first — your first question should show you've read the codedocs/plans/YYYY-MM-DD-<topic>-design.md. Otherwise, the conversation is the artifact.Do not jump to plan mode or implementation until the design direction is agreed.
Once the design is agreed, /iterate.
$ARGUMENTS