Freeze

This one pauses AI agent execution until you explicitly resume it, giving you a manual checkpoint in automated workflows. You'd use it when you want to review intermediate results before letting the agent continue, like checking data transformations before they get written to production or verifying API responses before the next chain of actions fires off. It's basically a human-in-the-loop pattern without having to rebuild your whole agent architecture. Simple concept, but genuinely useful when you're dealing with high-stakes operations or debugging agent behavior and need that moment to inspect state before things keep rolling.

skills.sh installs: 364
GitHub stars: 29.5K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add alirezarezvani/claude-skills --skill freeze --agent claude-code

Installs into .claude/skills of the current project.

Files

/c-level-agents:freeze — Cooldown Lock on a Decision

Command: /c-level-agents:freeze <decision-path> <days>

Locks a decision for a defined cooldown period. During the freeze, the chief-of-staff router refuses to re-litigate the decision unless a kill criterion explicitly triggers.

Inspired by gstack's /freeze and /guard safety primitives — adapted from code-scoping to strategic-scoping.

When to Use

Founders are pattern-matchers; pattern-matching after a tough decision often produces a reversal that's actually just decision fatigue. The freeze enforces a discipline:

After any irreversible or high-cost-to-reverse decision (fundraise, layoff, market entry)
After a split-vote boardroom (preserve the call against second-guessing)
After a founder gut-feel override of unanimous advisor consensus (let it run)
During a personnel transition (lock the strategy so the new exec can execute, not redebate)