Skip to main content

Weekly Digest

Every Monday morning, Scraut sends a stakeholder digest that summarises the previous week's progress, velocity trends, and upcoming sprint goals. This keeps managers and stakeholders informed without requiring status calls.

When it runs​

When: Every Monday at 8:00 AM (your configured timezone) Workflow: weekly-digest.yml Channels: #scraut-bot Slack channel + email (if configured)

Configuring the digest​

# workspace/scraut.yml
notifications:
  weekly_email: true
  stakeholder_emails:
    - cto@company.com
    - pm@company.com
    - alice@company.com  # team members can also receive it

Email requires SMTP secrets: SMTP_HOST, SMTP_PORT, SMTP_USER, SMTP_PASS.

What the digest contains​

The weekly digest is generated by reading:

  • Standup summaries from the past week (.scraut/sprint/NN/standup/summary/)
  • Sprint velocity from closed issues
  • Milestone health from .scraut/milestones/
  • Active suggestions from .scraut/suggestions/active/
  • Blocker count and resolution time

Example digest:

📊 Scraut Weekly Digest — Week of May 19–24, 2026
Team: Alice Smith, Bob Jones, Charlie Kim

═══════════════════════════════════════════════

🏃 SPRINT 01 — WEEK 1 OF 2

  Progress: 18 / 34 sp completed (53%)
  Goal: Deliver user authentication and basic dashboard
  Status: On track ✅

  This week's highlights:
  • OAuth integration merged (Alice, #21)
  • API rate limiting complete (Bob, #25)
  • Dashboard skeleton 60% done (Charlie, #28)

  Blockers this week: 1 (resolved within 2 days)
  • Alice: Needed design mockups — resolved Wed by designer Sarah

═══════════════════════════════════════════════

📈 VELOCITY

  Sprint 01 (in-progress): ~18 sp (projected 32 sp at current pace)
  Rolling average: N/A (first sprint)
  Trend: Establishing baseline

═══════════════════════════════════════════════

🎯 MILESTONE: v1.0 — Due Aug 31

  Status: On track ✅
  Progress: 2 of 4 epics started, 0 closed
  Forecast: Aug 24 (7 days early)

═══════════════════════════════════════════════

💡 SUGGESTIONS

  0 active suggestions (sprint 01 — building evidence)
  Check back after sprint review for first patterns

═══════════════════════════════════════════════

📅 NEXT WEEK

  Sprint 01 continues (8 days remaining)
  Grooming: Wednesday auto-run
  End of sprint: June 7

═══════════════════════════════════════════════

Sent by Scraut — text files in, automation out.
View live portal: https://myorg.github.io/my-repo/

Scenario: CTO reads digest instead of scheduling a meeting​

Characters: David (CTO), Alice (SM)

Before Scraut:

  • David scheduled a 30-minute weekly status meeting with Alice
  • Alice spent 1 hour preparing slides each Friday
  • Meeting was frequently rescheduled or went over time

After Scraut:

  1. David reads the Monday digest email (2 minutes)
  2. He sees the milestone is on track, velocity is healthy, one suggestion pending
  3. He replies to Alice: "Looks great — what's the story with the suggestion on PR review times?"
  4. Alice responds via email (2 minutes)
  5. No meeting needed

Time saved per week: ~2 hours (for Alice) + 30 minutes (for David).

Email digest formatting​

The email version is a formatted HTML email with:

  • A header with the team name and week date
  • Sections for sprint, velocity, milestones, and suggestions
  • A link to the live visibility portal
  • An "Unsubscribe" footer (managed via stakeholder_emails in scraut.yml)