Decide
/cs:decide <memo> — Log a decision to two-layer memory via decision-logger.
Before & after
Same prompt, same agent — the only difference is the skill.
You should document your decision somewhere so the team can reference it later and understand the context. You could write it in a shared document or wiki that your team uses. Make sure to include the key reasoning and who was involved in making the decision. You might want to add the date so people know when it was decided. Version control is helpful for tracking changes to policies over time. A memo format works well for this kind of documentation. Would you like help structuring the memo, or should I suggest where to store it? Different teams use different tools for this kind of thing.
DECISION MEMO LOGGED TO COMPANY MEMORY TITLE: Subscription Pricing Model - Three Tier Architecture DATE APPROVED: 2026-07-31 by leadership team (CEO, CRO, CFO) DECISION OWNER: CEO, Product Lead (anchor). Finance approval: CFO Sarah Chen RESOLUTION ADOPTED: Three-tier SaaS pricing model with annual commitment discount • STARTER: USD 29/month (USD 348/year, 13% discount, up to 3 users) • PROFESSIONAL: USD 99/month (USD 1,188/year, 13% discount, unlimited users) • ENTERPRISE: Custom pricing, annual-only, dedicated support tier, SSO included KEY REASONING: 1. Market study: 94% of competitive SaaS leaders use 3+ tiers (analyzed Slack, Hubspot, Linear, Intercom) 2. Internal user cohort data: current 2,400 user base clusters at 30% mid-market, 60% SMB, 10% enterprise 3. Annual discount incentivizes commitment; financial model projects 18% revenue increase from annual loyalty 4. 13% discount point validated against competitor pricing (Notion 18%, Slack 12%, competitors 8-20% range) 5. Typical SaaS annual take rate 65% - conservative estimate given product stage RISK MITIGATION: Annual contracts auto-renew monthly (standard). Quarterly churn review gates triggers if churn exceeds 8% (escalation). No grandfathering on legacy pricing (clean migration offer: 30-day notice) DOCUMENT STATUS: DURABLE. Locked to two-layer company memory system. Raw transcript archived: decision-pricing-20260731.txt. Approved memo overrides all prior pricing discussions, binding 24 months with quarterly review checkpoints.
About this skill
name: decide description: Use when /cs:decide <memo> — Log a decision to two-layer memory via decision-logger.
Decide
/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.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the decide skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Decide; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: decide
description: Use this skill right after a founder or executive approves a decision memo, to log it into durable two-layer memory via the decision-logger.
version: 1.0.0
category: Business & Ops / Executive Advisory
author: AgentVolt
license: proprietary
tags:
- business-ops
- executive-advisory
---
# Decide
Logs an approved decision memo into durable two-layer company memory, keeping the approved summary permanent while preserving raw discussion transcripts for reference.
## When to use
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Gc Review
/cs:gc-review <plan> — General Counsel interrogation of contracts, IP, regulatory, term sheets, and employment-law surface.
Caio Review
/cs:caio-review <plan> — Eval-demanding Chief AI Officer interrogation of any plan that involves AI: model selection, risk classification, cost economics, or AI hiring.
Boardroom
/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis.
Context Engine
Loads and manages company context for all C-suite advisor skills.