/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.
One skill from claude-skills.
shell
$ npx -y skills add alirezarezvani/claude-skills --skill execute --agent claude-codeInstalls just this skill. Get the whole plugin for auto-invocation.
How it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/execute
Context preview
The summary Claude sees to decide when to auto-load this skill.
/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.
Stats
Stars23,056
Forks3,139
LanguagePython
LicenseMIT
Ships with claude-skills
SKILL.md
execute.SKILL.md
--- 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]
