Weekly Summary

---
name: weekly-summary
description: >
  Summarises the week from local deal memory: who was contacted, who replied, who needs a
  follow-up, which deals are stuck. Triggered by "tổng kết tuần", "tuần này thế nào",
  "deal nào cần follow", "weekly summary", "review my pipeline", "what needs attention".
---

# Weekly summary

Read `<DATA>/deals/`, `<DATA>/follow-ups.md`, and `<DATA>/feedback.md`, then return a short table.

This is the thing a salesperson **wants to screenshot** — for their manager, their team, themselves.
Keep it tight and readable.

## How

1. Read `deals/index.md` for active deals.
2. Read `feedback.md` filtered to the period asked for (default: last 7 days).
3. Read `follow-ups.md` for overdue and upcoming items.
4. Count and group. **Never invent numbers** — only count what is actually in the files.

## Output

```markdown
### Tuần này (24/07 – 30/07)

- Đã liên hệ: 8 công ty
- Có phản hồi: 3
- Đã hẹn gặp: 1
- Đang chờ trả lời: 4

### Cần làm ngay
- [Quá hạn 2 ngày] ABC Logistics — follow-up proposal
- [Hôm nay] Minh An — gửi báo giá đã sửa

### Đang kẹt
- FPT — im lặng 12 ngày sau demo. Nên gửi break-up hoặc hẹn lại tháng sau.

### Sắp tới
- 02/08 — DEF Corp — gọi lần 2
```

Drop any section with no data. Nothing overdue → no "needs attention" section.
Headings follow the user's language.

## When there is no data

`<DATA>` is empty or has no deals:

```text
Mình chưa có deal nào trong bộ nhớ. Bắt đầu bằng cách viết email cho một khách,
rồi báo mình kết quả — từ tuần sau mình sẽ tổng kết được.
```

Never fabricate a report to look useful.

## Never

- Count anything not in the files.
- Derive a reply rate when the user has not reported enough outcomes.
- Mention opened emails or clicked links — **there is no tracking**.
- Write long. It must fit on a phone screen.

## Other periods

If the user asks for a month or quarter, also read the archive files per
`${CLAUDE_PLUGIN_ROOT}/policies/state-management.md`.