Help us improve
Share bugs, ideas, or general feedback.
From c-level-agents
/cs:decide <memo> — Log a decision to two-layer memory via decision-logger. Approved memo becomes durable; raw transcripts kept for reference.
npx claudepluginhub kruxshnx/claude-skills-devin --plugin c-level-agentsHow this skill is triggered — by the user, by Claude, or both
Slash command
/c-level-agents:decideThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Command:** `/cs:decide <memo-path>`
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Share bugs, ideas, or general feedback.
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.
/cs:office-hours → /cs:brief → /cs:boardroom → /cs:decide → /cs:execute → /cs:post-mortem
↑ you are here
The decision-logger skill maintains two layers:
~/.claude/decisions/raw/. Reference only, never feeds back automatically.~/.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.
A board memo file (output of /cs:boardroom).
~/.claude/decisions/approved/<YYYY-MM-DD>-<slug>.md~/company-vault/10-decisions/)# 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
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.
/cs:execute <decision> — build the 90-day plan/cs:freeze <decision> <days> — lock if irreversible/cs:post-mortem <decision> — at 90-day checkpointcs-chief-of-staff runs a weekly stale audit:
/cs:post-mortemdecision-loggercs-chief-of-staff../../references/llm-wiki-bridge.mdVersion: 1.0.0