Skills Product & Business Strategic Decision Freeze Lock

Strategic Decision Freeze Lock

v20261103
freeze
This skill implements a cooldown lock on irreversible strategic decisions to prevent decision fatigue and re-litigation. It enforces discipline for founders and C-level agents by blocking re-routing of topics during a defined period. Default periods vary by decision type, such as 30 days for fundraising or 90 days for market entry. Overrides require explicit founder action or trigger conditions.
Get Skill
367 downloads
Overview

/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)

Default Freeze Periods

Decision typeDefault freeze
Fundraise round size / lead choice30 days
Pricing change60 days
Market entry / exit90 days
Layoff / RIF30 days
Strategic pivot90 days
Personnel (exec hire / fire)60 days
M&A LOI30 days
Customspecify in command

Workflow

  1. Read the decision record
  2. Validate it has APPROVED status
  3. Apply freeze: write freeze_until: 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:

# Decision: <title>
...
**Status:** FROZEN
**Frozen until:** YYYY-MM-DD
**Reason for freeze:** <text>
**Override condition:** Kill criterion <name> triggers OR founder issues `/c-level-agents:freeze release` with stated reason

The active-freezes index is updated:

# Active Freezes
**Updated:** YYYY-MM-DD

| Decision | Frozen until | Override condition |
|---|---|---|
| <decision title> | YYYY-MM-DD | <kill criterion or /c-level-agents:freeze release> |

Override

To unfreeze before the period ends, the founder runs:

/c-level-agents:freeze release <decision> <reason>

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 /c-level-agents:post-mortem. The freeze does not protect against reality; it protects against impulse.

Why This Beats "Just Don't Re-Decide"

Founders have authority. Without an explicit lock + log, every wobble produces a "let's discuss this again" — which is exhausting for advisors and erodes the value of the boardroom. The freeze is a process, not a rule; it logs every override so the post-mortem can audit founder discipline.

Routing

  • /c-level-agents:freeze release — explicit early release
  • /c-level-agents:post-mortem — auto-triggered if kill criterion fires
  • /c-level-agents:boardroom — blocked until unfreeze or expiry

Related


Version: 1.0.0

Info
Name freeze
Version v20261103
Size 3.58KB
Updated At 2026-11-04
Language