Percerno Skillsbeta
← everything it can do · documents

Freeze DOCX

Locks a strategic business decision for a specified cooldown period to prevent impulsive reversals, updating the decision record status to FROZEN and maintaining an active-freezes index.

2 uses this weeksource alirezarezvanilicence MIT
Quality gate: FAIL · better answers · measured 2026-10-23
Blind-judged against the bare model on 2 requests: average lift -14.0 points (specificity, structure, method, fit).
won 0/2, lift -14.0, tokens ×117.5
Security scan: clean · 2026-10-24 · 1 files · ran in sandbox
no network calls, shell tricks, credential access or instruction tampering found in its files.

Try asking

Say it in your own words; the assistant finds this recipe by itself. Examples:

“Frys beslutningen om at skære 20% af marketingbudgettet i 30 dage.”
“Jeg har netop underskrevet LOI'en for opkøbet, så lås denne beslutning i 30 dage.”
“Anvend en 90 dages fryse på den strategiske pivot mod enterprise-kunder.”
“Freeze the decision to cut the marketing budget by 20% for 30 days.”
“I just signed the LOI for the acquisition, please lock this decision for 30 days.”
“Apply a 90-day freeze to the strategic pivot towards enterprise clients.”
Try this skill from Claude, ChatGPT or a chat on your own page. Free plan, no credit card.Get started free

Good for

strategic-decisioncooldownlockgovernancerisk-managementboardroomprocess-controlfounder-discipline

Not for

Do not use this skill for routine operational tasks, minor tactical adjustments, or decisions that are easily reversible. It is not a tool for creating new decisions or logging initial proposals; use the decision-logger skill for that purpose.

Details

When it is the right choice

Use this skill immediately after making a high-stakes, irreversible, or high-cost-to-reverse strategic decision such as a layoff, fundraise, or market entry. It is also appropriate when a decision was made under pressure, after a split board vote, or when a founder overrides advisor consensus to ensure the decision is not re-litigated due to fatigue or impulse.

The full recipe the assistant reads

/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 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 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:
  6. The freeze period expires, OR
  7. 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

Files in this skill (2)
  • LICENSE
  • SKILL.md
Where it comes from

Vendored from alirezarezvani/claude-skills, commit 27cfcd0fb0a4, path c-level-agents/skills/freeze, licence MIT. The upstream licence file ships inside the skill.