agentleFS
LwhieldonLwhieldon/claude-project-mgmt-playbook/.claude/skills/weekly-brief/SKILL.md

weekly-brief

Skill4 starsChanged 36 days agoMITView on GitHub

Monday brief for a project folder - what changed in the last 7 days, overdue and due-this-week actions, open decisions, and the meetings to prepare for. Read-only, safe to run on a schedule. Usage - /weekly-brief path/to/project-folder

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read a project folder and produce a short Monday brief: what changed, what is overdue, what is due, what is undecided, and what to prepare …

    line 8
  2. Distinctive:

    If nothing changed, say so in one line.

    line 37
  3. Very specific:

    Use [TBD] for any missing owner or date.

    line 62
  4. Distinctive:

    Do not open, write, or move any file.

    line 63
  5. Distinctive:

    If the folder contains another client's name in a file that is not that client's folder, flag it at the top of the brief under Check this.

    line 64

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Weekly Brief

Read a project folder and produce a short Monday brief: what changed, what is overdue, what is due, what is undecided, and what to prepare for. This skill reads and reports. It never writes files, never sends anything, and never changes a register. That is what makes it safe to run on a schedule.

Input

$ARGUMENTS is the path to a project folder, for example my-projects/acme or sample-projects/acme-data-warehouse. If no path was given, ask for one. If the folder does not exist, stop and say so; do not guess at a different folder.

Steps

  1. List the folder. Note every file and its last-modified date. Files touched in the last 7 days are "changed this week."
  2. Read the changed files plus any status CSV, action register, decision log, or meeting notes in the folder, whatever their date. Skip raw transcripts longer than a few pages unless a note or register does not exist; say if you skipped one.
  3. Find the dates. Collect every action item with a due date and every milestone date you can see. Compare against today's date. Anything due before today and not marked done is overdue.
  4. Find the open questions and decisions that appear in notes but have no recorded answer.
  5. Find the next meetings mentioned in notes or the calendar if one is in the folder.

Output

Weekly Brief: [project name] · week of [Monday's date]

What changed since last Monday

  • One line per file, newest first: filename, what it is, and the one thing worth knowing from it. If nothing changed, say so in one line.

Overdue

ActionOwnerWas dueSource file

Due this week

ActionOwnerDueSource file

Open decisions and questions

  • Each one with the file and date it was first raised. Oldest first.

Meetings to prepare for

  • Date, meeting, and the one-line suggestion for what /meeting-prep should focus on.

Suggested first task One sentence: the single thing the delivery lead should do first this morning, and why.

Generated by the weekly-brief skill on YYYY-MM-DD. Read-only; nothing was changed.

Rules

  • Report only what the files say. If the folder has no dates, say the brief cannot assess overdue items rather than inferring them.
  • Use [TBD] for any missing owner or date. Never assign one.
  • Do not open, write, or move any file. Do not create a summary file. The brief is the output.
  • If the folder contains another client's name in a file that is not that client's folder, flag it at the top of the brief under Check this.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.