agentleFS
sebssebs/rewelo/.claude/skills/standup/SKILL.md

standup

Skill2 starsChanged 50 days agoMITView on GitHub

Generate a daily standup digest with progress, blockers, and sprint health

55 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use close-day, meeting-prep and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • vantageos-agencySkill

    close-day

    End-of-day routine: close tasks with their time, leave the repository and the disk clean, write the diary, harvest friction, and hand over to tomorrow. Use this skill whenever the user says "close day", "end of day", "fin de journée", "bonne nuit", "wrap up", "call it a day", "close session", "daily close", or mentions ending their work session -- even if they don't say "close-day" explicitly.

    Also in 3 projects that use this

  • OpenAISkill

    meeting-prep

    Use when creating Public Equity Investing meeting prep briefs. Do not use for private diligence, IB, FP&A, legal, or scheduling-only tasks.

    Also in 5 projects that use this

  • jasonmichaelbell78-creatorSkill

    todo

    Cross-session todo management with interactive menu, JSONL-backed persistence, and AI-powered context capture. Manages ideas, tasks, and insights that emerge during sessions so they survive across sessions. Independent of GSD.

    Also in 3 projects that use this

  • takleb3rrySkill

    kickoff

    Initialize a new project by analyzing source documents and generating requirements.md and design.md

    Also in 3 projects that use this

  • asterkinSkill

    adr

    Create Architecture Decision Records (ADRs) following project standards. Guides template usage, process, and best practices for documenting architecturally significant decisions.

    Also in 4 projects that use this

  • GitHubSkill

    refactor

    Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 51 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use ticket_list with tags to get the tickets in each state, e.g.

    line 14
  2. Very specific:

    Use report_times for the cycle times of done tickets

    line 16
  3. Very specific:

    If tickets carry a sprint tag (e.g.

    line 38
  4. Distinctive:

    Keep it concise — this is a standup, not a report:

    line 45

“Common” is measured: kept by at least 6 in 10 of the 51 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

Daily Standup Digest

Generate a standup summary for project $0.

Data collection

  1. Use ticket_list with tags to get the tickets in each state, e.g. tags: ["state:wip"]: its items don't list tags. It returns 100 tickets per call: page with offset until you have total of them
  2. Use event_log with since (oldest first, 50 events per call: pass the last event's sequence as after for the next page, until a page is shorter than limit) for the transitions and when they happened: tag_added events with prefix state (value done in the last 24 hours for Done; the time a ticket got state:wip for how long it has been in progress)
  3. Use report_times for the cycle times of done tickets

Sections

Done (since last standup)

Tickets that transitioned to state:done in the last 24 hours. Show: title, cycle time, priority score.

In Progress

Tickets currently tagged state:wip. Show: title, how long in WIP, priority score. Flag any ticket in WIP for more than 3 days.

Blocked

Tickets tagged state:blocked (if tag exists). Show: title, how long blocked, priority score.

Up Next

Top 3 open tickets by priority that would fit remaining capacity: ticket_list with excludeTags: ["state:wip", "state:done", "state:blocked"] and sort: "priority". Open is as plan-sprint has it: a ticket without a state tag is in the backlog too, as new tickets have none until someone tags them.

Sprint Health (if applicable)

If tickets carry a sprint tag (e.g. sprint:2026-w39, as plan-sprint assigns), for the current sprint:

  • Total sprint tickets vs. completed (those also tagged state:done)
  • Priority-weighted progress: sum of (priority * done) / sum of priority for all sprint tickets
  • Projected completion based on current throughput

Output format

Keep it concise — this is a standup, not a report:

## Standup — Project Alpha — 2024-01-15

### Done (2)
- Login page redesign (3.2 priority, 2d cycle time)
- Fix password reset bug (4.1 priority, 0.5d cycle time)

### In Progress (3)
- Checkout flow (1.8 priority, 1d in WIP)
- API rate limiting (2.5 priority, 4d in WIP) ⚠️
- User dashboard (1.2 priority, 1d in WIP)

### Up Next
- Email notifications (3.0 priority, cost: 5)
- Export to CSV (2.1 priority, cost: 3)

### Sprint: 5/12 done (42%) | 60% by priority-weight

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.