90-Day Execution Plan
Turns an approved decision into a 90-day execution plan with weekly milestones, named DRIs, and a check-in cadence. It produces a structured markdown plan saved to a file, including workstreams, milestones, cadence, dependencies, risk register, and kill criteria watch.
✨ What it does
- Decomposes the chosen option into 3-6 workstreams with named DRIs.
- Reverse-engineers 12 weekly milestones from the checkpoint date.
- Sets cadence: weekly owner reviews, bi-weekly cross-functional syncs, and 30/60/90 checkpoints.
- Builds a risk register cross-referencing original devil's-advocate concerns.
- Includes kill criteria watch copied from the decision for checkpoint reviews.
- Saves the plan to ~/.claude/execution/YYYY-MM-DD-<slug>.md and notifies DRIs.
🎯 When to use it
- After a decision has been approved via /cs:decide and needs to become an actionable operating plan.
- When you need to assign owners (DRIs) and define weekly milestones for a strategic initiative.
- When you want to establish a check-in cadence and risk mitigation for a 90-day execution window.
🚀 How to use
Trigger: /cs:execute
Trigger with the slash command /cs:execute followed by the path to an approved decision record (output of /cs:decide). The skill reads the decision, decomposes it into workstreams, assigns DRIs, creates weekly milestones, sets cadence, builds a risk register, and saves the plan. Example prompts:
/cs:execute path/to/decision.md
/cs:execute decisions/2025-03-01-market-entry.md
📄 Output: A markdown execution plan file saved to ~/.claude/execution/YYYY-MM-DD-<slug>.md.
📦 Add this skill to Claude Code
# 1. Get the skills repo
git clone --depth 1 https://github.com/alirezarezvani/claude-skills /tmp/claude-skills
# 2. Copy this skill into your project (or ~/.claude/skills for all projects)
mkdir -p .claude/skills
cp -r /tmp/claude-skills/c-level-agents/skills/execute .claude/skills/executeSkill source: c-level-agents/skills/execute/SKILL.md
⚠️ Good to know
Requires an approved decision record from /cs:decide as input; it does not generate the decision itself.
❓ FAQ
What input does /cs:execute need?
It needs an approved decision record, typically the output of /cs:decide, which contains the chosen option and success/kill criteria.
How long is the execution plan?
The plan covers 90 days, with weekly milestones and checkpoints at day 30, 60, and 90.
What happens if kill criteria are triggered?
The kill criteria are reviewed at every checkpoint; if triggered, you can route to /cs:post-mortem or /cs:boardroom to re-decide.
🤖 Overview, features, install steps and FAQ were generated from the project's SKILL.md on Sep 4, 2026. Always check the original source before running commands.