القائمة
Use for reordering requested steps into dependency-correct execution order, ensuring optimal and safe operations regardless of the order instructions were provided.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | order-of-operations |
| description | Use for reordering requested steps into dependency-correct execution order, ensuring optimal and safe operations regardless of the order instructions were provided. |
MissionCore PrincipleScope BoundaryHard RuleTrigger ExamplesSequencing ModelIdeal Execution PhasesReordering RulesSafety-First OverridesValidation Ordering RulesParallelization RulesConflict ResolutionOperational Decision MatrixDocumentation SequencingEscalation ConditionsDeliverable FormatAnti-PatternsExecute work in the correct operational sequence, even when user instructions are listed in a non-optimal order.
Instruction order in a prompt is not automatically execution order. Execution order must follow:
Use this skill for explicit multi-step dependency sequencing and risk-aware reordering.
Do not invoke solely for trivial single-step tasks where baseline execution ordering is obvious.
Cross-skill handoff rule:
docs/skill-index.md before adding it to execution orderAlways follow the ideal order of operations when instruction order conflicts with required sequencing.
If explicit user ordering is unsafe or dependency-invalid:
Use this skill when requests contain:
For each requested action, classify:
Then build execution graph:
Use this default phase order unless context requires variation:
These operations must occur before risky mutation:
Never execute destructive or irreversible steps before safeguards. Never deploy by default.
Pre-validation dependency probe (required for expensive layers):
verify layer prerequisites first (runtime binaries, browsers, system libraries, network access)
if prerequisite is missing, switch to constrained verification protocol rather than repeatedly re-running blocked commands
run fast, cheap checks early
block expensive end-to-end tests when foundational checks fail
only proceed to next stage when prior gate passes or risk is explicitly accepted
Recommended validation sequence:
Constrained verification branch:
Parallelize only independent actions.
Can parallelize:
Do not parallelize:
Parallelization gate:
When explicit instructions conflict with ideal sequence:
If request includes:
Doc updates should follow validated implementation state. Order:
If documentation is prerequisite for safe operation (for example runbook execution), update before risky steps.
Pause and escalate when:
When applying this skill, provide:
Use for executing and enforcing governance tooling (artifact generation/validation/CI policy checks), including startup declaration checks, project-index sync checks, and repository skill-policy validation.
Use for converting ambiguous requests into explicit implementation contracts via assumptions, acceptance criteria, non-goals, constraints, and scope boundaries before major execution.
Use for selecting and enforcing the right process level across skills via deterministic risk scoring, mode-based gates, critical overrides, break-glass controls, ownership, and KPI review.
Use for minimizing token usage while preserving quality, through strict context filtering, indexed history retrieval, concise reasoning formats, output budgeting, and low-overhead execution patterns.
Use for managing the lifecycle of obsolete, superseded, merged, or renamed skills and docs with clear replacement paths, migration notes, validator warnings, and removal criteria.
Use for capping process overhead by task size, limiting skill count, validation depth, artifact creation, and user-facing ceremony before other governance or documentation skills expand scope.