agent-launcher-orchest…
Use when someone wants to build, launch, grade or schedule a Claude Managed Agent in their own Anthropic account ('build me an…
Use when logging a decision after a board meeting, reviewing past decisions or checking overdue actions. Keeps raw transcripts and approved decisions separately with decision_tracker.py.
Claude Code
$ npx -y skills add alirezarezvani/claude-skills --skill decision-logger --agent claude-code
Codex
$ npx skills add alirezarezvani/claude-skills --skill decision-logger -a codex -y
Cursor
$ npx skills add alirezarezvani/claude-skills --skill decision-logger -a cursor -y
Gemini CLI
$ npx skills add alirezarezvani/claude-skills --skill decision-logger -a gemini-cli -y
GitHub Copilot
$ npx skills add alirezarezvani/claude-skills --skill decision-logger -a github-copilot -y
OpenCode
$ npx skills add alirezarezvani/claude-skills --skill decision-logger -a opencode -y
Windsurf
$ npx skills add alirezarezvani/claude-skills --skill decision-logger -a windsurf -y
name: "decision-logger" description: "Use when logging a decision after a board meeting, reviewing past decisions or checking overdue actions. Keeps raw transcripts and approved decisions separately with decision_tracker.py." license: MIT metadata: version: 1.0.0 author: Alireza Rezvani category: c-level domain: decision-memory updated: 2026-03-05 python-tools: scripts/decision_tracker.py
Two-layer memory system. Layer 1 stores everything. Layer 2 stores only what the founder approved. Future meetings read Layer 2 only — this prevents hallucinated consensus from past debates bleeding into new deliberations.
decision log, memory, approved decisions, action items, board minutes, /decision-logger decisions, /decision-logger review, conflict detection, DO_NOT_RESURFACE
python scripts/decision_tracker.py --demo # See sample output python scripts/decision_tracker.py --summary # Overview + overdue python scripts/decision_tracker.py --overdue # Past-deadline actions python scripts/decision_tracker.py --conflicts # Contradiction detection python scripts/decision_tracker.py --owner "CTO" # Filter by owner python scripts/decision_tracker.py --search "pricing" # Search decisions
---
| Command | Effect | |---------|--------| | `/decision-logger decisions` | Last 10 approved decisions | | `/decision-logger decisions --all` | Full history | | `/decision-logger decisions --owner CMO` | Filter by owner | | `/decision-logger decisions --topic pricing` | Search by keyword | | `/decision-logger review` | Action items due within 7 days | | `/decision-logger review --overdue` | Items past deadline |
---
Storage follows the canonical two-layer decision memory (see `../agent-protocol/SKILL.md` → "Decision Memory (Canonical Layout)") — the same layout `/c-level-agents:decide` writes.
**Location:** `~/.claude/decisions/raw/YYYY-MM-DD-<slug>.md`
**Location:** `~/.claude/decisions/approved/` — one record per decision (`YYYY-MM-DD-<slug>.md`) plus the append-only index `decisions.md`
Migration: a legacy `memory/board-meetings/` folder may exist from earlier versions; read it for history but write all new entries to `~/.claude/decisions/`.
---
## [YYYY-MM-DD] — [AGENDA ITEM TITLE] **Decision:** [One clear statement of what was decided.] **Owner:** [One person or role — accountable for execution.] **Deadline:** [YYYY-MM-DD] **Review:** [YYYY-MM-DD] **Rationale:** [Why this over alternatives. 1-2 sentences.] **User Override:** [If founder changed agent recommendation — what and why. Blank if not applicable.] **Rejected:** - [Proposal] — [reason] [DO_NOT_RESURFACE] **Action Items:** - [ ] [Action] — Owner: [name] — Due: [YYYY-MM-DD] — Review: [YYYY-MM-DD] **Supersedes:** [DATE of previous decision on same topic, if any] **Superseded by:** [Filled in retroactively if overridden later] **Raw transcript:** ~/.claude/decisions/raw/[DATE]-<slug>.md
---
Before logging, Chief of Staff checks for: 1. **DO_NOT_RESURFACE violations** — new decision matches a rejected proposal 2. **Topic contradictions** — two active decisions on same topic with different conclusions 3. **Owner conflicts** — same action assigned to different people in different decisions
When a conflict is found:
⚠️ DECISION CONFLICT New: [text] Conflicts with: [DATE] — [existing text] Options: (1) Supersede old (2) Merge (3) Defer to founder
**DO_NOT_RESURFACE enforcement:**
🚫 BLOCKED: "[Proposal]" was rejected on [DATE]. Reason: [reason]. To reopen: founder must explicitly say "reopen [topic] from [DATE]".
---
1. Founder approves synthesis 2. Write Layer 1 raw transcript → `~/.claude/decisions/raw/YYYY-MM-DD-<slug>.md` 3. Check conflicts against `~/.claude/decisions/approved/decisions.md` 4. Surface conflicts → wait for founder resolution 5. Write the approved record to `~/.claude/decisions/approved/YYYY-MM-DD-<slug>.md` and append to the index `decisions.md` 6. Confirm: decisions logged, actions tracked, DO_NOT_RESURFACE flags added
---
- [x] [Action] — Owner: [name] — Completed: [DATE] — Result: [one sentence]
Never delete completed items. The history is the record.
---
~/.claude/decisions/ ├── raw/YYYY-MM-DD-<slug>.md # Layer 1: full transcript per meeting ├── raw/archive/YYYY/ # Raw files after 90 days ├── approved/YYYY-MM-DD-<slug>.md # Layer 2: one record per approved decision └── approved/decisions.md # Layer 2 index: append-only, founder-approved
---
411 production-ready skills for Claude Code and 12 other coding agents, covering engineering, product, marketing, compliance, finance and the C-suite. We test whether each skill loads when you ask in plain words, and publish the results.
Use when someone wants to build, launch, grade or schedule a Claude Managed Agent in their own Anthropic account ('build me an…
Use when a launched managed agent needs grading against a rubric and improving ('grade my agent', 'is it good enough'). Builds…
Use when someone has an agent idea to scope before launch ('help me scope an agent'). Interviews them about the one job and…
Use when a graded managed agent should run on a schedule, on an event trigger or on demand ('run it every morning'). Validates…
Use when a managed-agent build sheet is ready to launch ('launch it', 'deploy the agent'). Generates and validates API payloads…
Use when closing out a launched managed agent ('wrap up', 'what do I own now'). Inventories primitives with…
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid…
Design and build AI agents for any domain. Use when users: (1) ask to "create an agent", "build an assistant", or "design an AI…