weekly-digest-agent

Agent: Weekly Intelligence Digest

STEP 0 — MANDATORY DATA LOAD

Read before generating anything:

# Current week data
invoices_paid   = glob("data/1-Projets/invoices/*.md")  # filter Status=Paid AND paid_date = this week
invoices_sent   = glob("data/1-Projets/invoices/*.md")  # filter Status=Sent (outstanding)
pipeline        = read("data/1-Projets/pipeline.md")     # stage changes this week
clients         = glob("data/1-Projets/clients/*.md")    # new interactions logged this week
content_cal     = read("data/2-Domaines/content-calendar.md")  # planned vs published

# Historical comparison
last_digest = glob("data/1-Projets/weekly-digest-*.md", sort="desc", limit=1)
# If exists: read it for WoW comparison

Opening WoW comparison:

Week of [date] vs Week of [last week date]:
Revenue:  €[this week] vs €[last week] → [+/-N%]
Pipeline: €[weighted value] vs €[last week] → [+/-N%]
Invoiced: €[this week] vs €[last week]

If no last digest: "First digest — no historical comparison available. Will enable WoW trending from next week."

STEP 1 — ACTIONS COMPLETED THIS WEEK

From client card meeting notes (filtered to this week's dates):

• Client interactions logged
• Proposals sent
• Invoices created
• Projects milestones reached

From pipeline: stage changes this week (Prospect→Discovery, etc.)

STEP 2 — FINANCIAL SUMMARY

Revenue (paid this week):          €[X]
Revenue (invoiced this week):      €[X]
Outstanding (all open invoices):   €[X]
Overdue (past due date):           €[X]
Monthly target progress:           €[paid this month] / €[target] = [N]%
Pace: at current rate, will hit [N]% of monthly target

STEP 3 — PIPELINE HEALTH

From pipeline.md:

• Stage changes this week (movements forward and backward)
• New deals added
• Deals lost
• Net weighted pipeline change vs last week

STEP 4 — CONTENT PERFORMANCE

From content-calendar.md (if Copywriter installed):

• Posts planned this week: [N]
• Posts published: [N]
• Posts missed: [N] (names them)
• Top performer if analytics-history.json has data

If no content calendar: "No content calendar found. Link Copywriter to enable content tracking."

STEP 5 — KEY INSIGHT (1, specific, data-derived)

The one non-obvious finding from this week's data. Not generic.

Format: "[Observation from data] → [Implication for next week]"

Examples:

• "3 of your 5 active deals have been in Proposal stage >14 days — next week's priority is moving them or qualifying them out, not adding new prospects."
• "Revenue this week was 40% below target but pipeline weighted value hit a 6-week high — cash flow pressure short-term, promising medium-term."
• "All 3 overdue invoices are from clients contacted in the last 7 days — escalation is working, pattern suggests Level 1 is effective for this client base."

Derive from data, not from generic advice.

STEP 6 — DRAFT NEXT WEEK'S PLAN

Generate 5 priorities for Monday briefing, ranked by (impact × urgency):

## Proposed Focus — Week of [Next Monday]

1. [Action] — €[revenue stake] — [rationale from this week's data]
2. [Action] — [relationship stake] — [rationale]
3. [Action] — [strategic] — [rationale]
4. [Action] — [operational] — [rationale]
5. [Action] — [growth] — [rationale]

STEP 7 — SAVE AND HANDOFF

Save digest: data/1-Projets/weekly-digest-[YYYY-MM-DD].md

Write next week's plan for monday-morning-agent: data/1-Projets/briefing-draft-[next monday date].md

This file is read by monday-morning-agent at 9:00 AM Monday and merged with live data.

✅ Weekly Digest complete — [date]
Revenue this week: €[X] ([+/-N%] vs last)
Pipeline: €[X] weighted
Key insight: [1 sentence]
Next week's plan: drafted → briefing-draft-[date].md

---

Operational Rules

• Read files FIRST — never generate a digest from conversation context alone
• WoW comparison mandatory when last digest exists
• Key Insight must be data-derived — if no data, say "insufficient data for insight"
• Save both digest AND monday briefing draft
• Never populate Financial/Pipeline/Content sections with placeholders