# Execution Writing

> Create status reports, decision memos, and engineering execution plans that make progress, choices, ownership, dependencies, risks, and next actions clear.

- Skill: `bejeweledme/execution-writing` (Agent Skill)
- Install (CLI): `npx skillmds@latest add bejeweledme/execution-writing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/bejeweledme/execution-writing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: BejeweledMe (https://skillmd.com/u/bejeweledme)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/bejeweledme/execution-writing

---


# Execution Writing

Use this skill when the deliverable helps a team coordinate work, make a decision, or deliver an approved outcome. Choose one mode; do not invent progress, commitments, owners, dates, or confidence.

## Hierarchy And Handoffs

This is the primary owner for a status report, execution plan, or formal decision
memo. Use `information-decision-support` when the recommendation itself still needs
analysis, then package the result here for coordination and approval. Use
`audience-adaptation` to tune the artifact for executives or execution readers; do
not invent dates, owners, commitments, or progress while doing so.

## Status report mode

Report the actual state at a clear point in time. Use only sections that change the reader's understanding or action:

1. Overall status and reporting date.
2. Intended outcome, scope, or milestone.
3. Progress against plan or since the last relevant update.
4. Evidence: completed deliverables, metrics, or verified outcomes.
5. Blockers, risks, and dependencies.
6. Decisions, help, or approvals needed.
7. Next milestones, owners, and verification conditions when known.

Distinguish complete, in progress, planned, blocked, at risk, and unknown. Pair a status label with observable evidence or a concrete reason. Explain material variance from plan without narrating low-value activity.

## Decision memo mode

Lead with the decision requested or conclusion, then include only the background needed to act: why it matters, consequence of delay or inaction, constraints and criteria, evidence and realistic alternatives, recommendation and trade-offs, material risks and mitigations, and the requested approval or next action.

Use concrete numbers, time, cost, scale, and consequences where available. State what would change the recommendation when that condition is material.

## Execution plan mode

Cover the intended outcome, scope and non-goals, constraints and dependencies, work streams in delivery order, deliverables and handoffs, validation and operational readiness, risks and fallbacks, decision points, immediate next actions, and unresolved questions.

Sequence work by dependency and risk reduction. Make each material milestone verifiable by naming its success signal, test, review, or operational check. Separate confirmed commitments from proposals and unknown inputs.