alirezarezvani/freeze
c-level-advisor/c-level-agents/skills/freeze/SKILL.md
/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.
$ install --global
skillsauthnpx skillsauth add alirezarezvani/claude-skills freezeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 13, 2026, 4:12 AM75.3s1 file scanned
SKILL.md
- name:
- freeze
- description:
- /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.
/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
- Read the decision record
- Validate it has APPROVED status
- Apply freeze: write
freeze_until: YYYY-MM-DDto the decision record - Add to active-freezes index at
~/.claude/freezes/active.md - 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 `/cs:unfreeze` 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 /cs:unfreeze> |
Override
To unfreeze before the period ends, the founder runs:
/cs:unfreeze <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 /cs: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
/cs:unfreeze— explicit early release/cs:post-mortem— auto-triggered if kill criterion fires/cs:boardroom— blocked until unfreeze or expiry
Related
- Skill:
decision-logger - Agent:
cs-chief-of-staff— enforces freezes in routing
Version: 1.0.0
Related Skills
alirezarezvani/weekly-review
development
VerifiedTrustedCommunity
Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.
22,702SKILL.mdUpdated Jul 18, 2026
alirezarezvani/meetings
development
VerifiedTrustedCommunity
Use when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into owned action items — or says "should this be a meeting", "/cs:meeting-prep", or "/cs:meeting-actions". Runs a cost gate (ASYNC / NOT-READY / MEET), builds a decision-first agenda, and extracts an owner + due-date checklist that flags every orphan.
22,702SKILL.mdUpdated Jul 18, 2026
alirezarezvani/fable-goal
development
VerifiedTrustedCommunity
Convert a rambling description of a desired outcome into one polished, autonomous /goal prompt ready to paste into a fresh session. Use when the user says "/fable-goal", "turn this into a goal prompt", "write me a fable prompt", "write the prompt that builds X", or rambles about something they want made and asks for the prompt that makes it happen. The output is a single copy-paste prompt, never the build itself. Do NOT use when the user wants the thing built right now in this session — only when they want the PROMPT that will make it happen in a fresh session.
22,702SKILL.mdUpdated Jul 18, 2026
alirezarezvani/deep-work
development
VerifiedTrustedCommunity
Use when someone wants to plan a deep work day, time-block their calendar or task list, budget or cut shallow work, protect focus hours, track deep-work sessions and streaks, run an end-of-day shutdown ritual, or says "/deep-work" or "/time-block". Classifies tasks deep vs shallow, builds an energy-first time-blocked schedule that refuses deep demand past the 4-hour ceiling, batches shallow work into at most two windows, and logs focus sessions against a weekly target.
22,702SKILL.mdUpdated Jul 18, 2026