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

decide

Record founder-approved decisions with chosen options, success measures, stop conditions, and dissent. Keep approved decisions separate from discussion transcripts so future advisory sessions use confirmed choices, with a review scheduled after 90 days.

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

원문원문 설명 보기

/cs:decide <memo> — Log a decision to two-layer memory via decision-logger. Approved memo becomes durable; raw transcripts kept for reference. Use when the founder has approved a boardroom memo and the decision must become durable company memory — e.g. right after /cs:boardroom concludes.

설치 방법 보기

이럴 때 유용합니다

  • Recording an approved management decision
  • Preserving dissent and stop conditions
  • Scheduling a decision review after 90 days
  • Using past decisions in future advisory sessions

포함된 파일(1)

  • SKILL.md3.4 KB

SKILL.md(원문)

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

/cs:decide — Log the Decision

Command: /cs:decide <memo-path>

Logs the founder's decision via the decision-logger skill. This is the gate where in-session deliberation becomes durable company memory.

Pipeline Position

/cs:office-hours  →  /cs:brief  →  /cs:boardroom  →  /cs:decide  →  /cs:execute  →  /cs:post-mortem
                                                       ↑ you are here

Two-Layer Memory Model

The decision-logger skill maintains two layers:

  1. Raw transcripts — every boardroom session, every advisor's Phase 2 position, every dissent. Stored under ~/.claude/decisions/raw/. Reference only, never feeds back automatically.
  2. Approved decisions — only the founder-signed memos. Stored under ~/.claude/decisions/approved/. Feeds into future /cs:office-hours and /cs:founder-mode calls.

This split prevents the system from "remembering" unresolved debates as if they were decisions.

Input

A board memo file (output of /cs:boardroom).

Workflow

  1. Read the memo path
  2. Verify it has founder approval (status: APPROVED)
  3. Extract structured decision record:
    • Decision title
    • Date decided
    • Option chosen
    • Success + kill criteria
    • Dissent (preserved)
    • Review checkpoint date
  4. Append to ~/.claude/decisions/approved/<YYYY-MM-DD>-<slug>.md
  5. Update the raw transcript pointer
  6. If llm-wiki bridge configured, write to vault (~/company-vault/10-decisions/)
  7. Schedule auto-revisit (90 days)

Output Record Format

# Decision: <title>
**Decided:** YYYY-MM-DD
**By:** <founder name>
**Memo:** <link to boardroom memo>
**Brief:** <link to original brief>
**Review checkpoint:** YYYY-MM-DD (90d default)

## Decision
**Chose:** <option>
**Rejected:** <other options + one-line why>

## Success Criteria (binding)
- <metric, threshold, timeframe>

## Kill Criteria (binding)
- <metric, threshold, action>

## Preserved Dissent
- **<dissenter>:** <unresolved concern>
- (preserved verbatim; dissent never erased)

## Next Action
- `/cs:execute` → 90-day plan due <date>

## Status History
- YYYY-MM-DD: APPROVED

Why Preserved Dissent

The biggest risk in approved decisions is forgetting why someone disagreed. When the kill criteria trigger, the dissent often turns out to have been correct. Preserving it verbatim — not summarized — keeps the company honest at post-mortem time.

Routing

  • /cs:execute <decision> — build the 90-day plan
  • /cs:freeze <decision> <days> — lock if irreversible
  • (Auto-scheduled) /cs:post-mortem <decision> — at 90-day checkpoint

Stale-Decision Audit

cs-chief-of-staff runs a weekly stale audit:

  • Decisions > 90 days without revisit → flag for /cs:post-mortem
  • Decisions with kill criteria triggered → flag immediately
  • Decisions whose company-context.md basis has changed → flag for re-examination

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.8만2026년 8월 30일 업데이트

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.8만2026년 8월 30일 업데이트

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.8만2026년 8월 30일 업데이트

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.8만2026년 8월 30일 업데이트

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.8만2026년 8월 30일 업데이트

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.8만2026년 8월 30일 업데이트

alirezarezvani의 스킬 모두 보기

이 스킬의 문제 신고