القائمة
Standardize a plan — objective, assumptions, affected surfaces, steps, verification, rollback, open questions. Use when producing a plan, design proposal, or implementation outline.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Review code changes for correctness, error handling, scope creep, and style. Use when the goal mentions reviewing a PR, diff, or file.
Walk through a stack trace or error log to find the root cause. Use when the goal mentions debugging, investigating an error, or tracking down a bug.
Write a Conventional Commits message describing a code change. Use when the goal mentions creating a commit, writing commit message, or committing changes.
Outline unit tests for a function or module before writing them. Use when the goal mentions writing tests, test plan, or test coverage.
Keep effort proportional to risk — prefer the cheapest sufficient workflow, escalate only on evidence, refuse over-analysis on simple tasks. Use when choosing depth, level, or workflow shape.
Map required capabilities to persona roles and available skills. Detect missing skill coverage and decide whether to acquire a skill, request one, or proceed generically. Use when scoping a workflow.
| name | planning-contract |
| description | Standardize a plan — objective, assumptions, affected surfaces, steps, verification, rollback, open questions. Use when producing a plan, design proposal, or implementation outline. |
A useful plan is a contract: it states what will be true when the plan succeeds, what is assumed to make it work, and what would invalidate it.
A plan note in this exact shape: objective · assumptions · affected surfaces · steps · verification · rollback · open questions. Skip empty sections rather than invent content.
