← All craftbooks

Freeze Scope

Review and QAevalv1.3.1released 2026-09-01

Steps

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

1. Agree the frozen directoryplannerentry
   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 built-in write boundary is active: direct file mutations outside the frozen directory are denied automatically — you will see the denial as a tool error naming the boundary. Opaque built-in execution tools (`npm_install`, package/npx/Node/Playwright/installed scripts, `derive_file`, and project-type application) are blocked because their extra write targets cannot be proven. Custom project-type and third-party tools are not covered by this hook and must not be called while frozen. Work with direct workspace tools inside the directory. If the work genuinely needs an executor, custom tool, or outside path, do NOT fight the boundary: explain why and let the user widen `.gezel/freeze.json` or end this task.

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