القائمة
Explicitly limit blast radius before any implementation or file changes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Choose the smallest workflow that still buys back enough attention and safety for the task.
Record clear evidence that a task works, including commands, results, and remaining risks.
Compress project context into HANDOFF.md with workflow state, active modes, next gate, verification, current hypothesis, and resume packet for the next agent session.
Implement exactly one planned slice after scope is frozen.
Detect context drift, rehydration loops, hypothesis sprawl, scope creep, active-mode loss, and durable-state gaps. Recommend the smallest corrective action.
Create a compact SPEC.md that prevents premature agreement by defining intent, non-goals, likely failure modes, and verification evidence.
| name | scope-freeze |
| description | Explicitly limit blast radius before any implementation or file changes. |
Prevent uncontrolled changes by defining a narrow, enforceable boundary. This freezes write scope, not discovery.
Immediately before editing files or running state-changing commands.
Canonical output block:
SCOPE FREEZE
Task: ...
Allowed writes: ...
Read-only: ...
Forbidden: ...
Compatibility seams to preserve:
- Public imports / APIs: ...
- CLI behavior: ...
- Output schema: ...
- Fixture/data meaning: ...
- Existing tests that must remain meaningful: ...
Test integrity:
- Existing tests may be added to: yes/no
- Existing tests may be changed only if: ...
Review required if:
- tests changed
- dependencies changed
- protected paths touched
- compatibility seams changed
Allowed commands: ...
Stop when: ...
Invalid if: ...
The canonical block above.