agentleFS
aditya-jaiswaladitya-jaiswal/compound-os/.claude/skills/dsu-digest/SKILL.md

dsu-digest

Skill3 starsChanged 57 days agoMITView on GitHub

Turn daily standup updates (Slack or notes) into a structured team digest with accountability tracking. Use after the DSU.

The file

Files
SKILL.md

DSU Digest

From the standup input, produce:

  • Per person: what they did / doing / blockers.
  • Accountability check: anything promised previously that's now overdue (cross-check team/ and delivery/).
  • Cross-functional flags: dependencies, handoffs, things needing my decision.
  • Follow-ups for me: who I need to unblock, chase, or support today.

Save to team/dsu/YYYY-MM-DD.md. Capture recurring patterns (e.g. chronic blockers) into team/hypotheses.md.

Retention

Produce the digest only. Do NOT store raw standup transcripts (summary-first; see the retention policy in /log-call). Keep a rolling digest in team/dsu/.

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.