/cs:execute — 90-Day Execution Plan
Command: /cs:execute <decision-path>
Turns an approved decision into a 90-day plan with weekly milestones, named DRIs, and a check-in cadence. Where most decisions die: between "we decided" and "what's next Monday?"
Pipeline Position
/cs:office-hours → /cs:brief → /cs:boardroom → /cs:decide → /cs:execute → /cs:post-mortem
↑ you are here
Input
An approved decision record (output of /cs:decide).
Output Plan Format
Saved to ~/.claude/execution/YYYY-MM-DD-<slug>.md:
markdown# Execution Plan: <decision title> **Decision:** <link to /cs:decide record> **Owner (Sponsor):** <founder or exec> **Start:** YYYY-MM-DD **Checkpoint:** YYYY-MM-DD (90d) ## Outcome (binding) [Copied from decision: success + kill criteria] ## Workstreams | Workstream | DRI | Success Metric | Status | |---|---|---|---| | <e.g., Pricing rollout> | <name> | <metric, threshold> | Not started | | <e.g., Comms> | <name> | <metric> | Not started | | <e.g., Eng changes> | <name> | <metric> | Not started | ## Weekly Milestones | Week | Milestone | DRI | Definition of Done | |---|---|---|---| | 1 | <e.g., positioning locked> | <name> | <observable outcome> | | 2 | <e.g., draft launched> | <name> | <observable> | | 3 | ... | | | | 12 | <e.g., checkpoint review> | <name> | <observable> | ## Cadence - **Weekly:** Owner reviews status (15 min) - **Bi-weekly:** Cross-functional sync (30 min) - **Day 30 / 60 / 90:** Checkpoint with cs-chief-of-staff ## Dependencies - Internal: <list> - External: <vendors, regulators, customers> ## Risk Register | Risk | Likelihood | Impact | Owner | Mitigation | |---|---|---|---|---| | <e.g., delayed legal review> | M | H | <name> | <plan> | ## Kill Criteria Watch [Copied from decision; reviewed at every checkpoint] - <metric, threshold, action>
Workflow
- Read the decision record
- Decompose the chosen option into 3-6 workstreams
- Name a DRI for each workstream
- Reverse-engineer 12 weekly milestones from the checkpoint date
- Set the cadence (weekly + bi-weekly + 30/60/90 checkpoints)
- Build the risk register (cross-reference original Phase 4 devil's-advocate concerns)
- Save and notify DRIs
Why 90 Days
- Long enough to show real signal (not just activity)
- Short enough to course-correct before damage compounds
- Matches quarterly OKR cycle, fundraise sprints, and most board cadences
Routing
/cs:post-mortem <decision>— at day 90 (or earlier if kill criteria trigger)/cs:boardroom— if a checkpoint reveals a need to re-decide
Related
- Skills:
coo-advisor,strategic-alignment,change-management - Agent:
cs-coo-advisor
Version: 1.0.0
AgenticMarket