Agent skill · alirezarezvani
freeze
/cs:freeze <decision> <days> — Lock a strategic decision for a cooldown period to prevent impulse reversal. Mirrors gstack's safety primitives for the business layer. Use when an irreversible decision was made under pressure — e.g. a layoff plan or multi-year contract — and deserves a cooling-off lock before execution.
What it needs
About 2k tokens when loaded.
What this skill does
/cs:freeze — Cooldown Lock on a Decision Command: /cs: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) Default Freeze Periods Decision type Default freeze --- --- Fundraise round size / lead choice 30 days Pricing change 60 days Market entry / exit 90 days Layoff / RIF 30 days Strategic pivot 90 days Personnel (exec hire / fire) 60 days M&A LOI 30 days Custom specify in command Workflow 1. Read the decision record 2. Validate it has APPROVED status 3. Apply freeze: write freezeuntil: YYYY-MM-DD to the decision record 4. Add to active-freezes index at ~/.claude/freezes/active.md 5. cs-chief-of-staff router now refuses to re-route this topic to the boardroom until: The freeze period expires, OR A kill criterion explicitly triggers Output The decision record is updated in place: The active-freezes index is updated: Override To unfreeze before the period ends, the founder runs: The unfreeze is logged in the decision history (preserved permanently). Forced overrides create a paper trail that surfaces at post-mortem. Auto-Override If a kill criterion in the decision triggers, the freeze auto-releases and the chief-of-staff routes immediately to /cs:post-mortem. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alirezarezvani/freeze--4f9f51