Skip to main content

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.

Informations de source

Dépôt
alirezarezvani/claude-skills
Dernière activité de la source
21 août 2026 à 05:47
Langue détectée de SKILL.md
anglais
Étoiles
28 245
Forks
3 977

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

Affichage de SKILL.md

SKILL.md
Instructions source · Aperçu en lecture seule
name
execute
description
/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.
# /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 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`](../../../c-level-advisor/skills/coo-advisor/SKILL.md), [`strategic-alignment`](../../../c-level-advisor/skills/strategic-alignment/SKILL.md), [`change-management`](../../../c-level-advisor/skills/change-management/SKILL.md) - Agent: [`cs-coo-advisor`](../../agents/cs-coo-advisor.md) --- **Version:** 1.0.0
Voir sur GitHub