mcpField
E
execute

execute

github.com/alirezarezvaniProductivity28.9k376 installsUpdated 2d ago
Repository

About execute

execute is a Claude skill that turns an approved decision into a 90-day execution plan. It organizes workstreams, assigns directly responsible individuals, sets weekly milestones and check-ins, and records risks.

Key features

  1. 01Converts decisions into 90-day plans
  2. 02Breaks work into 3–6 workstreams
  3. 03Assigns a DRI to each workstream
  4. 04Creates 12 weekly milestones
  5. 05Sets check-ins and a risk register

Use cases

  1. 01Putting an approved decision into action
  2. 02Assigning owners across workstreams
  3. 03Tracking weekly progress toward a checkpoint
  4. 04Reviewing risks before a 90-day post-mortem

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/alirezarezvani/claude-skills --skill execute

After installing, type/executein Claude Code to confirm it loaded.

Details

From the project README

/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:

# 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

  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

Version: 1.0.0

Comments

Markdown supported