agentleFS
Sign inStart free
loremaster-ailoremaster-ai/loremaster/skills/daily-scrum/SKILL.md

daily-scrum

Skill4 starsChanged 4 months agoMITView on GitHub

Runs the daily scrum in the SM role when mentioned or explicitly asked ("daily"/"scrum") — designed as a daily 10:00 cron (currently unregistered; manual operation): checks the previous day's progress against the Jira backlog + lore vault and asks each team member confirmation questions; strictly read-only (never modifies backlog or vault), never runs conflict checks (that is the explicit conflict-detection invocation's job); this channel = this project only.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. Ujrep/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository11 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Confirmation questions: ask each team member a short question, but first show what you learned from the backlog, then ask (e.g., "Yesterday …

    line 27
  2. Distinctive:

    Never modify the backlog directly: When needed, delegate a proposal to backlog-update.

    line 33
  3. Distinctive:

    No evaluation, no blame. Focus on fact synchronization + surfacing blockers.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Daily Scrum (SM)

SM role that synchronizes progress in the same format every day. Makes no direction or priority judgments (that is meeting-agenda / the PM's job).

Behavior

  1. Core injection (read): Jira backlog state (this project) + the lore vault (narrow to relevant concepts with graphify query, then read). Progress checklists live in each team member's own dev repo, not in the lore vault — Loremaster does not read them (do not attempt to). Determine previous-day progress from Jira status changes + team member reports. Do not look at conflicts/ (conflict checking is not the daily's job).
    • Enrich with linked context via graphify (structure): look up in-progress items with graphify query "<item/concept>" --graph graphify-out/graph.json and graphify explain "<concept>" to identify the concepts each item depends on or connects to (decisions or prerequisite features that could cause a blockage). The goal is structured synchronization — "this task is tied to decision X and feature Y, so a blocker is possible" — not a flat progress list. Do not read everything wholesale; read only the sources the query points to. If graph.json is missing, fall back to direct reads.
  2. Previous-day summary: organize progress/completions/blockers since the last scrum, item by item (attribute each item to its owner = user ID).
  3. Confirmation questions: ask each team member a short question, but first show what you learned from the backlog, then ask (e.g., "Yesterday the [[login]] PR looks merged — any remaining blockers?").
  4. Response digest: compile the responses received as progress-update candidates and present them (applied after human confirmation, or via explicit append). Do not write directly.

Scope & Rules (invariants)

  • This channel = this project only. No mentioning or referencing other projects.
  • The purpose is progress synchronization. Do not handle direction, priorities, or estimation.
  • Never modify the backlog directly. When needed, delegate a proposal to backlog-update.
  • No conflict checks and no conflict-verdict reminders. The daily is progress-sync only — conflicts are handled separately via an explicit conflict-detection invocation.
  • Do not invent progress that has no basis in the backlog. If you do not know, turn it into a question.
  • No evaluation, no blame. Focus on fact synchronization + surfacing blockers.

Output

  • Post the daily summary + per-member confirmation questions to the Slack channel. (No automatic meeting minutes; no automatic progress writes.)

Unattended execution (cron) caution

  • (No cron is currently registered — manual operation. This section prepares for future cron registration.)
  • Once registered in cron, this skill runs daily with no human present. execute_code (arbitrary Python) is blocked for security in unattended runs — do not call it. Read files directly with read_file/search_files (grep).

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.

Check your setup, free