Percerno Skillsbeta
← everything it can do · documents

Decide DOCX

Logs a founder-approved boardroom memo into durable company memory by extracting structured decision records and storing them in the approved decisions directory. It preserves dissent and schedules future review checkpoints.

2 uses this weeksource alirezarezvanilicence MIT
Quality gate: FAIL · better answers · measured 2026-10-23
Blind-judged against the bare model on 2 requests: average lift -21.5 points (specificity, structure, method, fit).
won 0/2, lift -21.5, tokens ×239.4
Security scan: clean · 2026-10-24 · 1 files · ran in sandbox
no network calls, shell tricks, credential access or instruction tampering found in its files.

Try asking

Say it in your own words; the assistant finds this recipe by itself. Examples:

“Logg beslutningen fra memoen i /memos/2023-10-01-pivot.md”
“Boardroom-mødet er slut, og jeg har godkendt strategien. Gem denne beslutning i hukommelsen.”
“/c-level-agents:decide /sti/til/godkendt-memo.md”
“Log the decision from the memo at /memos/2023-10-01-pivot.md”
“The boardroom is done and I approved the strategy. Please save this decision to memory.”
“/c-level-agents:decide /path/to/approved-memo.md”
Try this skill from Claude, ChatGPT or a chat on your own page. Free plan, no credit card.Get started free

Good for

decision-loggingmemory-managementboardroomfounder-approvalstrategyrecord-keepinggovernancepost-mortem-prep

Not for

Do not use this skill for unapproved or draft memos, as it requires an 'APPROVED' status. It is not for executing the strategic plan itself (use /c-level-agents:execute) or for conducting the initial strategic discussion (use /c-level-agents:boardroom). It is not for general note-taking or meeting minutes that do not involve a formal decision record.

Details

When it is the right choice

Use this skill immediately after a boardroom session concludes and the founder has explicitly approved a memo. It is the correct step to convert temporary deliberation into permanent, structured company knowledge. It is also used when a specific approved memo file needs to be formally registered in the decision log.

The full recipe the assistant reads

/c-level-agents:decide — Log the Decision

Command: /c-level-agents: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

/c-level-agents:office-hours  →  /c-level-agents:brief  →  /c-level-agents:boardroom  →  /c-level-agents:decide  →  /c-level-agents:execute  →  /c-level-agents: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 /c-level-agents:office-hours and /c-level-agents:founder-mode calls.

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

Input

A board memo file (output of /c-level-agents:boardroom).

Workflow

  1. Read the memo path
  2. Verify it has founder approval (status: APPROVED)
  3. Extract structured decision record:
  4. Decision title
  5. Date decided
  6. Option chosen
  7. Success + kill criteria
  8. Dissent (preserved)
  9. Review checkpoint date
  10. Append to ~/.claude/decisions/approved/<YYYY-MM-DD>-<slug>.md
  11. Update the raw transcript pointer
  12. If llm-wiki bridge configured, write to vault (~/company-vault/10-decisions/)
  13. 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
- `/c-level-agents: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

  • /c-level-agents:execute <decision> — build the 90-day plan
  • /c-level-agents:freeze <decision> <days> — lock if irreversible
  • (Auto-scheduled) /c-level-agents: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 /c-level-agents: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

Files in this skill (2)
  • LICENSE
  • SKILL.md
Where it comes from

Vendored from alirezarezvani/claude-skills, commit 27cfcd0fb0a4, path c-level-agents/skills/decide, licence MIT. The upstream licence file ships inside the skill.