Guide · Agent skill
How to use the Log Founder Decisions agent skill (decide)
Updated · written with AI from the project's own documentation and checked against our catalogue data
The decide skill is a step in a company-style decision workflow for Claude Code and compatible agents. After a founder approves a board memo, it turns that memo into a structured decision record and saves it as durable company memory. This guide explains what the skill does, how to install it, how to trigger it with natural requests, and what it needs before you rely on it.
Log Founder Decisionsalirezarezvani/claude-skills · MIT Download the skill Quick start
- 1Install the c-level-agents plugin. Make sure the c-level-agents plugin and its decision-logger skill are installed, since decide depends on them.
- 2Download the decide ZIP. Download the ZIP from the skill page on this site.
- 3Unzip into a skills folder. Unzip into ~/.claude/skills/ for personal use, or into .claude/skills/ inside a project. In the Claude apps, upload the ZIP under Settings, then Capabilities, then Skills.
- 4Produce and approve a board memo. Run /c-level-agents:boardroom and get the founder's approval, so the memo status reads APPROVED.
- 5Run the decide command. Run /c-level-agents:decide with the path to the approved memo, or ask the agent in natural language to log the decision.
- 6Check the output. Confirm the record in ~/.claude/decisions/approved/ and check the chosen option, criteria, dissent and 90-day review date.
What the decide skill does
The decide skill, invoked as /c-level-agents:decide with a memo path, logs the founder's decision through the decision-logger skill. It is the point where in-session deliberation becomes durable company memory.
The skill keeps two layers. Raw transcripts of boardroom sessions, advisor positions and dissent are stored under ~/.claude/decisions/raw/ for reference only and never feed back automatically. Approved decisions, which are only founder-signed memos, are stored under ~/.claude/decisions/approved/ and feed into future office-hours and founder-mode calls. This split keeps unresolved debates from being remembered as decisions.
- Reads the board memo and checks that its status is APPROVED
- Extracts the decision title, date, chosen option, rejected options, success and kill criteria, preserved dissent and review checkpoint
- Appends the record to approved/ using a date-and-slug file name
- Updates the pointer to the raw transcript
- Writes to the llm-wiki vault at ~/company-vault/10-decisions/ if the bridge is configured
- Schedules an automatic revisit at 90 days
Install the decide skill
Download the ZIP from the skill page on this site. The skill's files are included in the download, and the main file is SKILL.md.
Option 1: unzip the download into ~/.claude/skills/ so it is available across your projects. Option 2: unzip it into the .claude/skills/ folder of a single project so it applies only there.
Option 3: in the Claude apps, open Settings, then Capabilities, then Skills, and upload the ZIP there.
- Personal install: ~/.claude/skills/
- Project install: .claude/skills/ inside the project folder
- Claude apps: Settings → Capabilities → Skills
Check the prerequisites before you run it
The decide skill does not work on its own. It depends on the surrounding c-level-agents plugin, because the commands and referenced files it calls, including boardroom, decision-logger and cs-chief-of-staff, must be present. Without them it will not work as described.
You also need a board memo file produced by /c-level-agents:boardroom with APPROVED status, and write access to ~/.claude/decisions/. The llm-wiki bridge is optional and only needed if you want records written to ~/company-vault/10-decisions/.
- Claude Code or a compatible agent with the c-level-agents plugin installed
- Access to the decision-logger skill at vendor/c-level-advisor/decision-logger
- A board memo with APPROVED status from /c-level-agents:boardroom
- Write access to ~/.claude/decisions/
- Optional: llm-wiki bridge configured to write to ~/company-vault/10-decisions/
Trigger the skill with a natural request
The skill's description says to use it when the founder has approved a boardroom memo and the decision must become durable company memory, for example right after /c-level-agents:boardroom concludes. Pass the memo path to the command directly.
Plain requests such as asking the agent to log the approved decision in the memo, or to record the decision from the boardroom memo, should match the skill's purpose. Naming the memo file makes the match more reliable.
- Log the approved decision in boardroom-memo.md
- Record this decision as durable company memory
- Save the approved boardroom memo to the decision log
/c-level-agents:decide <memo-path>Read the decision record it produces
The output is a markdown record with a title, decided date, founder name, links to the memo and original brief, and a review checkpoint dated 90 days out by default. It lists the chosen option and rejected alternatives with a one-line reason each.
Success criteria and kill criteria are marked binding. Preserved dissent is recorded verbatim, not summarized, so each dissenter's unresolved concern stays on record. The record also includes a next action pointing to /c-level-agents:execute and a status history starting with APPROVED.
- Chose and Rejected options
- Success Criteria (binding) and Kill Criteria (binding)
- Preserved Dissent, verbatim
- Next Action and Status History
# Decision: <title>
**Decided:** YYYY-MM-DD
**Review checkpoint:** YYYY-MM-DD (90d default)Safety notes: scripts, network and storage
According to the skill's listing, it runs no scripts and uses no network access. Its records are written to your home directory under ~/.claude/decisions/, and to an external vault only if you configure the optional llm-wiki bridge.
Because decision records contain strategy, review where they are stored before using the skill with sensitive material. Storing them in ~/.claude or an external vault may not be acceptable for every organization.
- Runs scripts: no
- Uses network: no
- Writes to ~/.claude/decisions/ by default
- Writes to ~/company-vault/10-decisions/ only if the llm-wiki bridge is configured
Tips for getting good results
Only run the skill on memos that carry APPROVED status. The skill checks for this and the record is meant to reflect a founder decision, not a draft.
Keep the memo path handy and make sure the memo's success and kill criteria are specific before approving, since they are carried into the record as binding. After the record exists, the stale-decision audit in cs-chief-of-staff can flag decisions that pass 90 days without revisit or whose kill criteria have triggered.
- Approve the memo before logging it
- Write specific, measurable success and kill criteria
- Keep dissent in the memo so it is preserved verbatim
- Use the stale-decision audit to catch decisions due for review
What people use it for
- Recording a pricing or hiring decision right after a boardroom session concludes, with the rejected options noted
- Keeping a written audit trail of why a product choice was made and who disagreed
- Scheduling a 90-day checkpoint so the team reviews the decision with its kill criteria in view
- Feeding approved decisions into future office-hours sessions so the agent works from settled choices, not open debates
Frequently asked questions
Is the decide skill free?
The skill is published under the MIT licence, as listed on its page. Check the licence file in the repository for the full terms before redistributing it.
How do I install the decide agent skill?
Download the ZIP from the skill page and unzip it into ~/.claude/skills/ for all projects or into a project's .claude/skills/ folder. In the Claude apps, upload the ZIP under Settings, then Capabilities, then Skills.
What do I need to run decide?
You need Claude Code or a compatible agent with the c-level-agents plugin, access to the decision-logger skill, a board memo with APPROVED status from /c-level-agents:boardroom, and write access to ~/.claude/decisions/. The llm-wiki bridge is optional.
Does decide run scripts or use the internet?
According to the skill's listing, it runs no scripts and uses no network. It writes records to your home directory, and to an external vault only if the optional llm-wiki bridge is set up.
Can I use decide without the boardroom command?
The skill expects a memo produced by /c-level-agents:boardroom with APPROVED status. Quick personal choices or unapproved drafts are not a good fit, because the skill expects that approved memo as its input.
What is the difference between raw transcripts and approved decisions?
Raw transcripts hold boardroom sessions, advisor positions and dissent for reference and do not feed back automatically. Approved decisions hold only founder-signed memos and feed into future office-hours and founder-mode calls.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use decide if you run the c-level-agents advisory pipeline and want approved decisions recorded consistently, with dissent and kill criteria preserved for later review. Pick something else if you do not have the surrounding plugin, want to log quick personal choices, or cannot store decision records in ~/.claude or an external vault.
Download the skill