freeze
by alirezarezvanifreeze is a Claude chief-of-staff skill for locking high-cost strategic decisions during a cooldown period. Use /cs:freeze <decision-path> <days> to prevent re-litigation unless clear kill criteria trigger.
This skill scores 68/100, which means it is acceptable for directory listing but should be presented as a lightweight procedural decision-discipline skill rather than a fully implemented enforcement tool. Directory users can understand when to use it and what command to call, but should expect to supply their own persistence, routing, and operational controls.
- Clear trigger and syntax: `/cs:freeze <decision-path> <days>` is easy for an agent to recognize and invoke.
- Useful business-governance niche: it defines cooldown locks for high-cost decisions such as fundraising, layoffs, market entry, pivots, and executive personnel choices.
- Includes default freeze periods by decision type, giving agents more concrete guidance than a generic prompt would provide.
- No support files, scripts, README, or install command are provided, so adoption depends entirely on the single SKILL.md file.
- The lock appears procedural rather than enforceable; the evidence does not show persistent state, integration with a router, or concrete kill-criterion handling mechanics.
Overview of freeze skill
What freeze does
The freeze skill is a strategic planning control for Claude-based chief-of-staff workflows. It uses the command /cs:freeze <decision-path> <days> to lock a major decision for a defined cooldown period so the agent does not keep re-litigating it after the call has already been made.
This is most useful when a founder, executive team, or board has made a costly decision under pressure and needs execution discipline rather than another round of anxious reconsideration.
Best fit for Strategic Planning decisions
Use freeze for Strategic Planning when the decision is high-cost, high-emotion, or hard to reverse: fundraise terms, layoffs, pricing changes, market entry or exit, strategic pivots, executive hiring or firing, M&A LOIs, or major customer commitments.
The skill is not a generic productivity timer. Its value is in making an AI advisor respect a decision boundary unless a predefined kill criterion is met.
What makes the freeze skill different
A normal prompt can say “don’t revisit this decision,” but the freeze skill gives that instruction a structured operating role: lock the decision, define the duration, and refuse re-analysis during the freeze unless exception conditions are triggered.
The repository is intentionally lightweight: the core behavior is in SKILL.md, with no extra scripts, rules, or reference files. That makes it easy to inspect, but it also means teams should add their own decision logs, escalation rules, and governance context if they need auditable process.
How to Use freeze skill
freeze install and repository review
To install the skill in a compatible skills workflow, use:
npx skills add alirezarezvani/claude-skills --skill freeze
Then inspect the source file directly:
c-level-advisor/c-level-agents/skills/freeze/SKILL.md
Because this skill has no supporting rules/, resources/, references/, or scripts/ folders, SKILL.md is the main implementation contract. Read the “When to Use,” “Default Freeze Periods,” “Workflow,” and “Output” sections before relying on it for a live leadership decision.
freeze usage pattern
The command format is:
/cs:freeze <decision-path> <days>
A weak call is vague:
/cs:freeze pricing 60
A stronger call gives the agent enough context to know what is locked:
/cs:freeze "Lock decision to increase self-serve pricing by 18% for new customers only; do not reopen packaging strategy unless churn exceeds 4.5% monthly or sales conversion drops below 22%" 60
The second version is better because it names the decision, scope, duration, and exception triggers. Without that detail, the agent may block useful analysis or allow too many loopholes.
Turn a rough goal into a complete prompt
For reliable freeze usage, include five inputs:
- Decision: what is locked.
- Scope: what is and is not included.
- Freeze duration: number of days.
- Reason for lock: why reconsideration is risky now.
- Kill criteria: objective conditions that allow reopening.
Example:
/cs:freeze "Proceed with EMEA market entry through UK-first launch; freeze alternatives including Germany-first and partner-only entry. Reason: board approved UK plan after split vote and team needs execution focus. Reopen only if launch costs exceed approved budget by 25%, legal blocker appears, or first 3 enterprise pilots fail qualification." 90
Suggested workflow after invoking freeze
After calling the skill, ask the agent to produce a freeze record: decision summary, start date, end date, owner, allowed execution questions, blocked re-litigation questions, and kill criteria.
During the freeze window, route questions differently. “Should we still do this?” should be refused or redirected. “How do we execute the locked decision?” should be allowed. This distinction is the practical difference between strategic discipline and blind rigidity.
freeze skill FAQ
When should I not use freeze?
Do not use freeze for decisions that are still under discovery, legally uncertain, ethically questionable, or missing basic evidence. The skill is for protecting an already-made strategic call, not for forcing premature commitment.
It is also a poor fit for reversible day-to-day choices, creative brainstorming, product copy, or routine prioritization. In those cases, a normal planning prompt is simpler and safer.
Is freeze beginner-friendly?
Yes, if you understand the decision you are locking. The command itself is simple, but the quality depends on how clearly you define scope and exceptions. Beginners should start with a short freeze period and explicit kill criteria rather than locking a broad strategy for months.
For leadership teams, the skill works best when paired with a written decision memo or board note.
How is this better than an ordinary prompt?
An ordinary prompt can ask Claude not to reconsider something once. The freeze skill makes that refusal a reusable behavior inside a chief-of-staff workflow. It tells the agent that revisiting the decision is not a normal analysis request during the lock period.
That distinction matters when executives repeatedly ask variations of the same question after a stressful call.
Does freeze make decisions irreversible?
No. It creates a cooldown lock, not a permanent ban. The repository’s framing allows reopening when a kill criterion explicitly triggers. The safest use is to define those criteria before emotions rise again, not after the team wants a different answer.
How to Improve freeze skill
Improve freeze inputs with measurable triggers
The most common failure mode is a freeze with no clear exception path. Replace subjective triggers like “if things go badly” with observable ones:
- “Pipeline conversion falls below 18% for two consecutive weeks”
- “Cash runway drops below 9 months”
- “Legal counsel blocks the proposed structure”
- “Customer churn exceeds the agreed threshold”
This helps the agent distinguish disciplined execution from denial of new evidence.
Add decision records around freeze
Because the upstream skill is a single SKILL.md file, teams should add their own operating wrapper: decision owner, approver, date, affected teams, freeze end date, and evidence considered. Store that in your normal planning system, not only in chat.
A useful format is:
- Decision locked
- Rationale
- Alternatives rejected
- Freeze period
- Kill criteria
- Execution questions still allowed
- Review date
Iterate after the first output
After invoking freeze, ask the agent to audit the lock:
“List any ambiguity in this freeze that could cause over-blocking, under-blocking, or unsafe refusal to consider new evidence.”
Then revise the decision path. Good freezes are narrow enough to preserve execution momentum and specific enough to allow real risk signals through.
Adapt freeze for your governance level
For a solo founder, a simple 30- or 60-day freeze may be enough. For a board-level decision, add approval authority and escalation rules. For sensitive decisions such as layoffs, M&A, or executive exits, do not let the skill substitute for legal, HR, financial, or fiduciary review.
The strongest version of freeze is not “never reconsider.” It is “do not reopen this decision casually; only reopen it under the conditions we defined when we were thinking clearly.”