weekly-brief-for-education

Weekly Brief for Education

Overview

Produces and maintains a recurring weekly brief for an education role (educator, department lead, or institutional leader). It reconciles this week's calendar, meeting notes, mail, chats, and working files against the previous brief, so decisions, owners, and unresolved questions carry forward instead of being re-derived each week.

When to Use

• The user runs a weekly planning or review ritual and wants the same brief refreshed
• The user asks what changed, what they committed to, or what is at risk this week
• The user wants next week's priorities derived from this week's evidence

When NOT to Use

• A recap of one specific meeting — use meeting-intel instead
• A same-day catch-up on mail and Teams — use daily-briefing instead
• A message written for an audience (team, leadership, parents) — use stakeholder-comms instead
• Anything involving individual student records or staff performance judgments

Shared Skill Contract

This skill follows the institution's shared contract for every run:

1. Intent check — confirm outcome, audience, timeframe, and format before working.
2. Source plan — show the sources selected, their date ranges, access gaps, and freshness.
3. Clarification gate — ask only for missing information that would change the result.
4. Staged execution — keep discovery, synthesis, creation, review, and finalization separate.
5. Reviewable output — separate facts, interpretation, recommendations, assumptions, and open questions.
6. Human approval — require confirmation before sending, publishing, or changing any record.
7. Reusable state — carry accepted decisions forward without silently reusing stale assumptions.
8. Quality check — run the checks below before presenting final output.
9. Telemetry — log workflow signals only; never sensitive content.
10. Failure behavior — explain missing access, unsupported sources, uncertainty, and partial completion.

Core Instructions