---
name: eod-eow
description: Write end-of-day (EOD) and end-of-week (EOW) team status messages. Answer-first with executive summary, achievements, blockers, next steps.
---

## Before writing

Read the most recent EOD. Cross-check open items against what the user has told you. **Ask about anything open that hasn't been addressed** — do not drop threads silently.

## Shared principles (EOD + EOW)

Both formats follow the same rules:

- **Answer-first.** Lead with the conclusion. Do not bury it.
- **Output, not activity.** Every bullet must pass the "so what?" test. If the reader needs to infer whether this is good news, rewrite it.
- **Name the knock-on effect.** Blockers are useless without impact. State what is blocked, why it matters, and who needs to act.
- **All next steps need an owner.** Orphaned actions get ignored.
- **Max 5 bullets per section.** Fewer is better.
- **No filler.** Cut "great progress", "productive day", "as mentioned".

| Activity (bad) | Output (good) |
|---|---|
| "Continued investigation of the bug" | "Root cause identified — fix in progress" |
| "Spent two days on the auth spec" | "Auth spec finalized — ready for review" |
| "Got most questions answered" | "Design questions resolved — spec finalized" |

**Slack formatting:** `_italic_` for date header, `*bold*` for section titles, `@Name` for mentions, backticks for code, emoji only for culture moments.

---

## EOD — End of Day (daily)

A short daily update. Read by people with multiple projects. It is also for you — it forces reflection on what you achieved, what is next, and what needs escalation.

```
_End of Day — DD.MM.YYYY (Weekday)_

[Optional: personal note]

[Executive summary — 1-2 sentences: are we on track?]

**[Section title — conclusion, not topic]**

- What happened
- How it happened (if non-obvious)
- Why it matters (if high-stakes)

**Blockers** ← omit if none

- [Blocker]: what is blocked
- [Ask]: who needs to act, by when

**Next Steps**

- [2-3 items for tomorrow, each with an owner]
```

**Section titles** are conclusions, not labels:

| Good | Bad |
|---|---|
| Auth Module — 90% Complete | Auth Module |
| Reporting API — Blocked on Review | Status Update |

**Write for 5-10 minutes.** Keep it under 15 lines.

**File:** `eod/EOD-YYYY-MM-DD.md` in the project root.

---

## EOW — End of Week (Friday)

A weekly summary. Read by leads, clients, and stakeholders. Answers: **what was the net result of this week, and why does it matter for next week?**

Two formats. Use Option A for stakeholder-heavy weeks. Use Option B for quieter weeks.

### Option A: Pyramid Principle

Open with a one-sentence **governing conclusion** — the verdict on the week, not an activity list.

```
_Week of DD–DD Month YYYY_

[Governing conclusion. Not "what we did" — "what it means".]

[Optional: one-line context — where are we process-wise, what changed?]

_[Cluster 1 title — conclusion]_

- Key accomplishment + why it matters
- Change since last week (if notable)

_[Cluster 2 title]_ ...  _[Cluster 3 title]_ ...

---

_Next Week_

[2-4 bullets: what this sets up, key meetings/dates, named owners, open items]
```

| Activity summary | Verdict |
|---|---|
| "This week we worked on auth, reports, and testing." | "Auth module at 90% and tests passing — release on track." |
| "We had a productive week." | "All three tracks advanced with no blockers." |

Clusters by: **impact** (default) → **chronological** (narrative arc) → **problem → solution → risk** (one challenge dominated).

### Option B: Achievements & Priorities

Two headings, 3-5 bullets each. Best for individual contributors or quiet weeks.

```
_Week of DD–DD Month YYYY_

[Optional: one-line context]

**Achievements this week** (max 5)  →  **Priorities next week** (max 5)  →  **Key meetings / dates**  →  **Open / Need Help**
```

### What changed since last week

This is the single most valued element by senior stakeholders. If timelines shifted, blockers cleared, or new findings emerged — call it out explicitly.

### Open items (both formats)

```
**Open / Need Help With**

- Staging environment — blocked since Tuesday, infra-side. @lead escalating. Any ETA?
- New hire admin rights — ticket with IT. Can this be prioritized Monday?
```

**File:** `eod/EOW-YYYY-MM-DD.md` (Friday's date) in the project root.

---

## Pitfalls

- **Too many priorities.** Max 5. If only one thing matters, list one.
- **Too verbose.** Each bullet should be one line. Long updates get skipped.
- **Activity, not output.** "Worked on X" is not an achievement. "Shipped X" is.
- **Dropped threads.** If blocked yesterday and still blocked today, say so. Silence erodes trust.
- **No named owners.** Next steps without owners are wishes.

## Checklist

- [ ] Read previous EOD — ask about anything unaddressed
- [ ] Dates absolute (DD.MM.YYYY), titles are conclusions, next steps have owners
- [ ] No filler phrases
- [ ] Risks and blockers explicit with named asks

**EOD:** Executive summary first. Blockers named (or omitted). 2-3 next steps. 5-10 min write time.

**EOW:** Governing conclusion is the first sentence — verdict, not activity. Max 5 per section. Open items at the bottom. Call out what changed.