Percerno Skillsbeta
← everything it can do · finance

Execute TEXT

Generates a structured 90-day execution plan from an approved decision, including weekly milestones, named Directly Responsible Individuals (DRIs), workstreams, and check-in cadences.

2 uses this weeksource alirezarezvanilicence MIT
Quality gate: PASS · better answers · measured 2026-10-23
Blind-judged against the bare model on 2 requests: average lift +2.5 points (specificity, structure, method, fit).
won 1/2, lift +2.5, tokens ×19.24
Security scan: clean · 2026-10-24 · 1 files · ran in sandbox
no network calls, shell tricks, credential access or instruction tampering found in its files.

Try asking

Say it in your own words; the assistant finds this recipe by itself. Examples:

“Lav en 90-dages eksekveringsplan ud fra den godkendte beslutning om at gå ind på det tyske marked.”
“/c-level-agents:execute ~/.claude/decisions/2023-10-01-prisændring.md”
“Vi har besluttet at lancere den nye API. Opret ugentlige milepæle og tilordn ansvarlige for næste kvartal.”
“Turn the approved decision to enter the German market into a 90-day execution plan.”
“/c-level-agents:execute ~/.claude/decisions/2023-10-01-pricing-change.md”
“We decided to launch the new API. Create the weekly milestones and assign DRIs for the next quarter.”
Try this skill from Claude, ChatGPT or a chat on your own page. Free plan, no credit card.Get started free

Good for

execution-plan90-day-planmilestonesdriproject-managementdecision-implementationcadencerisk-registerstrategic-operations

Not for

Do not use this skill for creating initial strategic briefs or decision documents, as it requires an existing approved decision as input. It is not suitable for long-term multi-year roadmaps or short-term daily task lists. Use the 'decide' or 'brief' skills for upstream strategic formulation, and 'post-mortem' for downstream review.

Details

When it is the right choice

Use this skill when a strategic decision has been formally approved and needs to be translated into an actionable operating plan. It is ideal for bridging the gap between a high-level boardroom decision and day-to-day team execution. It is specifically designed for scenarios requiring a 90-day horizon with defined checkpoints and accountability.

The full recipe the assistant reads

/c-level-agents:execute — 90-Day Execution Plan

Command: /c-level-agents: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

/c-level-agents:office-hours  →  /c-level-agents:brief  →  /c-level-agents:boardroom  →  /c-level-agents:decide  →  /c-level-agents:execute  →  /c-level-agents:post-mortem
                                                                       ↑ you are here

Input

An approved decision record (output of /c-level-agents:decide).

Output Plan Format

Saved to ~/.claude/execution/YYYY-MM-DD-<slug>.md:

# Execution Plan: <decision title>
**Decision:** <link to /c-level-agents: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

  • /c-level-agents:post-mortem <decision> — at day 90 (or earlier if kill criteria trigger)
  • /c-level-agents:boardroom — if a checkpoint reveals a need to re-decide

Related

Version: 1.0.0

Files in this skill (2)
  • LICENSE
  • SKILL.md
Where it comes from

Vendored from alirezarezvani/claude-skills, commit 27cfcd0fb0a4, path c-level-agents/skills/execute, licence MIT. The upstream licence file ships inside the skill.