Agent skill · alirezarezvani

execute

/cs:execute <decision> — Generate a 90-day execution plan with weekly milestones, DRIs, and check-in cadence from an approved decision. Use when a logged decision needs to become an operating plan — e.g. turning an approved market-entry call into weekly milestones with DRIs.

What it needs

About 2k tokens when loaded.

What this skill does

/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 Input An approved decision record (output of /cs:decide). Output Plan Format Saved to ~/.claude/execution/YYYY-MM-DD-<slug>.md: Workflow 1. Read the decision record 2. Decompose the chosen option into 3-6 workstreams 3. Name a DRI for each workstream 4. Reverse-engineer 12 weekly milestones from the checkpoint date 5. Set the cadence (weekly + bi-weekly + 30/60/90 checkpoints) 6. Build the risk register (cross-reference original Phase 4 devil's-advocate concerns) 7. 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

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills alirezarezvani/execute--bc5b62

View the source on GitHub

Browse the @skills marketplace