القائمة
Break complex work into ordered subgoals with explicit dependencies, expected outputs, and stopping conditions. Use when a task has multiple steps, unclear scope, or non-trivial coordination.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | task-decomposition |
| description | Break complex work into ordered subgoals with explicit dependencies, expected outputs, and stopping conditions. Use when a task has multiple steps, unclear scope, or non-trivial coordination. |
A plan that is too coarse hides the failures; a plan that is too fine drowns them. Decompose to the level where each subgoal has a checkable output.
A short tree or numbered list: subgoal · expected output · dependencies · done-when. No more depth than the work warrants.
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.
