Businessalirezarezvani-skills
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.
3k est. installs25k stars
Estimated installs are a discovery signal based on public repository popularity and source completeness, not recorded Dokki installation events.
Repository
alirezarezvani/claude-skills
Pinned commit
f2bac0a8f29b
License
MIT
Execution
Instructions only
Complete source instructions
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
Two-Layer Memory Model
The decision-logger skill maintains two layers:
- Raw transcripts — every boardroom session, every advisor's Phase 2 position, every dissent. Stored under
~/.claude/decisions/raw/. Reference only, never feeds back automatically. - Approved decisions — only the founder-signed memos. Stored under
~/.claude/decisions/approved/. Feeds into future/cs:office-hoursand/cs:founder-modecalls.
This split prevents the system from "remembering" unresolved debates as if they were decisions.
Input
A board memo file (output of /cs:boardroom).
Workflow
- Read the memo path
- Verify it has founder approval (status: APPROVED)
- Extract structured decision record:
- Decision title
- Date decided
- Option chosen
- Success + kill criteria
- Dissent (preserved)
- Review checkpoint date
- Append to
~/.claude/decisions/approved/<YYYY-MM-DD>-<slug>.md - Update the raw transcript pointer
- If llm-wiki bridge configured, write to vault (
~/company-vault/10-decisions/) - Schedule auto-revisit (90 days)
Output Record Format
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
- Skill:
decision-logger - Agent:
cs-chief-of-staff - Bridge:
../../references/llm-wiki-bridge.md
Version: 1.0.0
Same repository
Related Skills
agent-launcher-orchestrator
Use when a user wants to build, launch, grade, or schedule a Claude Managed Agent (CMA) in their own Anthropic account — "build me an agent", "launch this as a managed agent", "run this on a schedule", "grade my agent against a rubric", "set up a nightly worker". Reads the per-session goal (./my-agent/goal.json), routes deterministically to one of five phase sub-skills (interview → stage-launch → grade-iterate → run-without-you → wrap-up) via goal_router.py, and compiles the goal+phase into an execution shape (single-pass workflow / bounded grade→iterate loop / recurring cron deployment loop) via loop_compiler.py. Forks context so heavy intake (build sheets, payloads, eval cases) stays out of the parent thread. All launches are emitted as BYOK curl the user runs with their own key; no tool makes API calls. Inspired by anthropics/launch-your-agent (Apache-2.0). Distinct from engineering/agent-harness (generic domain loop) and engineering/write-a-skill (authors Claude Code skills, not CMAs).
View detailsagent-protocol
Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.
View detailsarquiteto-de-empresa
Company Architect: builds a business from scratch as an OKF (Open Knowledge Format) bundle — a tree of version-controllable .md files with frontmatter type, links forming a graph, and reserved index.md/log.md, readable by humans and agents. Guides the founder through a 12-phase interview (foundation, strategy, market, financial, sales, marketing, product, operations, tech, people, legal, governance), one phase at a time, few questions per block, and generates the concepts as conformant markdown. Trigger when the user wants to create, structure, or document an entire company in folders and .md files; when they mention build my company from scratch, company as code, company knowledge base for AI to read, company wiki for agents, OKF, or knowledge bundle. In English.
View detailsarquiteto-de-empresa
Company Architect: builds a business from scratch as an OKF (Open Knowledge Format) bundle — a tree of version-controllable .md files with frontmatter type, links forming a graph, and reserved index.md/log.md, readable by humans and agents. Guides the founder through a 12-phase interview (foundation, strategy, market, financial, sales, marketing, product, operations, tech, people, legal, governance), one phase at a time, few questions per block, and generates the concepts as conformant markdown. Trigger when the user wants to create, structure, or document an entire company in folders and .md files; when they mention build my company from scratch, company as code, company knowledge base for AI to read, company wiki for agents, OKF, or knowledge bundle. In English.
View detailsboard-deck-builder
Assembles comprehensive board and investor update decks by pulling perspectives from all C-suite roles. Use when preparing board meetings, investor updates, quarterly business reviews, or fundraising narratives. Covers structure, narrative framework, bad news delivery, and common mistakes.
View detailsboard-meeting
Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes /cs:boardroom, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question.
View details