← All craftbooks

Freeze Scope

Review and QAevalv1.0.1released 2026-07-25

Steps

Entry step: set-boundary. Each step names the specialist role it wants; the full working prompt is expandable.

1. Agree the frozen directorydeveloperentry
   Show working prompt

   Confirm with the user which single workspace directory edits are allowed in — use `ask_user_question` if the kickoff didn’t name one. Then record it by writing `.gezel/freeze.json` with exactly:
   
   ```json
   { "dir": "<workspace-relative-directory>" }
   ```
   
   Use a relative path with no leading `./` and no trailing slash (e.g. `src/billing`). Tell the user the freeze is on and advance.

2. Freeze activedeveloper
   Show working prompt

   The write boundary is active: any write outside the frozen directory is denied automatically — you will see the denial as a tool error naming the boundary. Do the scoped work normally inside the directory. If the work genuinely needs to touch something outside, do NOT fight the boundary: tell the user what needs changing and why, and let them either widen `.gezel/freeze.json` deliberately or end this task to lift the freeze.

Triggers

Phrases that suggest this craftbook to a crew.

• freeze scope
• only touch
• stay inside
• lock edits to

Source

View this craftbook on GitHub · MIT license