Master Daily Suite

A comprehensive skill for generating structured daily operational documents — including daily standup summaries, shift handover reports, daily planning templates, and end-of-day status digests for teams and individual contributors.

When to Use This Skill

Choose Master Daily Suite when you need to:

• Generate consistent daily standup reports from raw notes
• Create shift handover documents with structured context transfer
• Build daily planning templates with prioritized task lists
• Produce end-of-day status summaries for stakeholders
• Automate recurring daily documentation workflows

Consider alternatives when:

• You need weekly or monthly reporting (use a periodic reporting skill)
• You're managing project timelines (use a project management skill)
• You need meeting minutes from live conversations (use a transcription skill)

Quick Start

Copy
# Generate a daily standup summary
claude "Create a daily standup summary for a 5-person engineering team. Yesterday: deployed auth service v2.1, fixed cart timeout bug. Today: starting payment gateway integration, code review backlog. Blockers: staging environment is down."

Copy
# Daily Standup — Engineering Team
**Date**: 2024-12-15 | **Sprint**: Sprint 24.12.2

## Yesterday's Accomplishments
- ✅ Deployed auth service v2.1 to production (no incidents)
- ✅ Resolved cart session timeout bug (JIRA-1247)

## Today's Plan
- 🔵 Begin payment gateway integration (JIRA-1302)
- 🔵 Clear code review backlog (4 PRs pending)

## Blockers
- 🔴 Staging environment down since 08:30 — DevOps investigating
  - **Impact**: Cannot run integration tests for payment gateway
  - **ETA**: Awaiting update from @infra-team

## Team Availability
| Member   | Status      | Focus Area            |
|----------|-------------|-----------------------|
| Alice    | Available   | Payment gateway       |
| Bob      | Available   | Code reviews          |
| Carol    | PTO (back 12/17) | —                |
| Dave     | Available   | Auth service monitoring|
| Eve      | Half-day    | Staging investigation |

Core Concepts

Daily Document Types

Document Type	Purpose	Audience
Standup Summary	Team sync on progress and blockers	Engineering team
Shift Handover	Context transfer between shifts	Incoming shift team
Daily Plan	Individual task prioritization	Self + manager
Status Digest	Executive progress snapshot	Stakeholders, leadership
Operations Log	Incident and event tracking	Operations, SRE

Shift Handover Template

Copy
# Shift Handover Report
**Outgoing Shift**: Day Shift (06:00-18:00)
**Incoming Shift**: Night Shift (18:00-06:00)
**Date**: 2024-12-15

## Active Issues
| Issue          | Status       | Next Step              |
|---------------|--------------|------------------------|
| DB replication | Monitoring   | Check lag at 20:00     |
| CDN cache miss | Investigating| Review logs in /var/log|

## Completed During Shift
- Patched CVE-2024-XXXXX on web servers 1-4
- Deployed hotfix for user session expiry

## Pending Actions for Incoming Shift
1. Monitor DB replication lag (alert threshold: >5s)
2. Complete CDN log analysis and escalate if cache hit <80%
3. Approve deployment queue (2 services pending)

## Environment Status
| System     | Health | Notes              |
|-----------|--------|--------------------|
| Production | 🟢     | All services normal|
| Staging    | 🔴     | Down for maintenance|
| CI/CD      | 🟡     | Queue backed up    |

Priority Framework

Copy
## Daily Task Prioritization (Eisenhower Matrix)

### 🔴 Urgent + Important (Do First)
- Production incidents, blocker resolution
- Deadline-critical deliverables

### 🟡 Important + Not Urgent (Schedule)
- Feature development, technical debt
- Documentation, testing improvements

### 🔵 Urgent + Not Important (Delegate)
- Routine requests, standard approvals
- Non-critical communications

### ⚪ Neither (Eliminate)
- Low-value meetings, redundant reports

Configuration

Parameter	Description	Example
document_type	Type of daily document to generate	"standup" / "handover"
team_size	Number of team members	5
include_metrics	Add quantitative metrics section	true
format	Output format	"markdown" / "slack"
timezone	Team timezone for timestamps	"America/New_York"
sprint_id	Current sprint identifier	"Sprint 24.12.2"

Best Practices

1. Keep standup summaries scannable in under 30 seconds — Use bullet points, status icons (✅ 🔵 🔴), and tables instead of paragraphs. The reader should grasp yesterday, today, and blockers at a glance without reading full sentences.

2. Include impact and ETA for every blocker — A blocker without context is useless. Always state what the blocker prevents, who owns resolution, and the expected resolution time. This lets leadership assess urgency without follow-up questions.

3. Separate facts from opinions in handover reports — "DB replication lag is 3.2 seconds" is a fact. "I think the lag might cause issues tonight" is an opinion. Label both clearly so the incoming team can prioritize based on data.

4. Time-box daily document creation to 10 minutes — If it takes longer, the template is too complex. Daily documents should capture essential state, not comprehensive analysis. Save deep analysis for weekly reviews.

5. Archive daily documents with consistent naming — Use YYYY-MM-DD-type naming (e.g., 2024-12-15-standup.md) for easy retrieval. Teams that lose historical dailies lose the ability to trace decisions and patterns.

Common Issues

Daily reports become copy-paste from yesterday — When teams reuse the same status for days, the document loses value and people stop reading it. Add a "days unchanged" counter for any item that repeats more than twice. If a task has been "in progress" for 5 days, it needs escalation, not another copy-paste.

Handover reports miss critical context — The outgoing shift knows things that seem obvious but aren't written down. Use a structured checklist that forces explicit status for every monitored system, rather than free-form notes that skip "obvious" items. What's obvious at 5pm isn't obvious at 2am.

Status digests are too detailed for leadership — Executives need 3-5 bullet points, not a full engineering log. Create separate templates for technical teams (detailed) and leadership (summary). Auto-generate the executive summary from the detailed version by extracting only items tagged as stakeholder-relevant.