본문으로 건너뛰기
cccskills
무료GitHub에 공개

freeze

Set a cooling-off period for an approved strategic decision, keeping it out of repeated debate until expiry or a defined exception. It records freeze dates and early-release reasons so later reviews can trace changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

/c-level-agents: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.

설치 방법 보기

이럴 때 유용합니다

  • Holding a fundraising decision steady for a set period
  • Preventing repeated debate after a pricing decision
  • Preserving a decision made after a divided board vote
  • Keeping strategy stable during an executive transition

포함된 파일(1)

  • SKILL.md3.8 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

/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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Audit web applications for accessibility issues against WCAG 2.2 Level A and AA, the web accessibility standards. Get framework-specific code fixes, contrast checks, verification steps, and reports, with options for automated checks in development pipelines.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Audit a web application before release
  • Fix contrast and keyboard navigation issues
  • Prepare accessibility reports for stakeholders
alirezarezvani/claude-skills2.9만2026년 10월 21일 업데이트

Plan A/B tests that compare page variations, from headlines to pricing layouts. Define a hypothesis, choose success metrics, calculate sample size and duration, and prepare launch checks and results reports to support decisions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Comparing landing page headlines
  • Testing signup button changes
  • Planning pricing page experiments
alirezarezvani/claude-skills2.9만2026년 10월 21일 업데이트

Create paid ad headlines and body copy tailored to each platform's character limits. Use existing performance data to develop variations, explore new messaging angles, and check copy for length, quality, and potential rejection risks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Creating Google RSA headlines
  • Writing Meta and LinkedIn ad copy
  • Developing variations of successful ads
alirezarezvani/claude-skills2.9만2026년 10월 21일 업데이트

Review code changes from three critical perspectives: production failures, maintainability, and security. Get a consolidated report that ranks findings by severity and provides merge guidance, helping examine assumptions that an ordinary self-review may overlook.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Reviewing a pull request before merging
  • Getting a second opinion on AI-written code
  • Checking authentication or data access code
alirezarezvani/claude-skills2.9만2026년 10월 21일 업데이트

aeo

무료

Audit and improve content intended for citation in AI answers. Review evidence, author information, and structure, generate revised content and structured metadata, and keep a local record of observed citations across AI services.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Audit existing articles for evidence and credibility gaps
  • Revise article structure and references for AI answers
  • Record citations observed across AI services
alirezarezvani/claude-skills2.9만2026년 10월 21일 업데이트

Create signed records for consequential agent actions such as deployments, deletions, and payments. Decide which actions need evidence, record the agent, action, target, and policy, then verify the resulting certificate offline to detect later changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Creating signed records for production deployments
  • Preserving evidence of deletions and payments
  • Recording access grants for later review
alirezarezvani/claude-skills2.9만2026년 10월 21일 업데이트

alirezarezvani의 스킬 모두 보기

이 스킬의 문제 신고