agentleFS
Sign inStart free
lglucaslglucas/ai-dev-operating-system/.claude/skills/daily-standup/SKILL.md

daily-standup

Skill12 starsChanged 47 days agoMITView on GitHub

At the start of a session (or on user request "o que a gente fez", "onde paramos"), produce a four-part briefing — what's done, what's in progress, what's next, what's blocked. Replaces the dev habit of standup for solo vibe coders.

16 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

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

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 3

    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:

    After returning from a break of more than a few hours.

    line 12
  2. Distinctive:

    Before closing a sprint.

    line 13
  3. Distinctive:

    Use "a gente" (1ª pessoa do plural) — você é parte do time.

    line 42
  4. Very specific:

    Use linguagem simples. Sem feat:, merge, branch aqui — isso é pra leitura rápida.

    line 43

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

When to run this skill

  • First message of a new session for a project (auto-trigger).
  • User says: "onde paramos" / "o que tá rolando" / "me lembra o que tava fazendo" / "resumo".
  • After returning from a break of more than a few hours.
  • Before closing a sprint.

Inputs

  • Last entries in session-log/.
  • Last commits (git log --oneline -10).
  • docs/SPRINTS.md or current sprint doc.
  • CHANGELOG.md recent entries.

Output format (four sections, plain Portuguese)

☀️ Bom dia. Onde a gente parou:

✅ Feito ontem (ou na última sessão):
   • [1-3 itens concretos]

🚧 Em andamento agora:
   • [1-2 itens com % aproximada]

🎯 Próximo passo (o que faria sentido fazer agora):
   • [1 item, prazo curto]

🚨 Bloqueios / decisões esperando você:
   • [se houver — caso contrário "nada bloqueando"]

Tone

  • Use "a gente" (1ª pessoa do plural) — você é parte do time.
  • Use linguagem simples. Sem feat:, merge, branch aqui — isso é pra leitura rápida.
  • Se houve algo arriscado na última sessão, marque com 🟡.

Example

☀️ Bom dia. Onde a gente parou:

✅ Feito ontem:
   • Configuração inicial do banco (Supabase) feita
   • Tela de login funcionando com magic link
   • Email de boas-vindas testado

🚧 Em andamento:
   • Tela de dashboard (~40% — falta a parte dos cards de métricas)

🎯 Próximo passo:
   • Terminar os 3 cards do dashboard. Estimativa: 1-2h.

🚨 Bloqueios:
   • Você precisa decidir se a primeira métrica é "clientes novos" ou "receita do mês". Te mando uma comparação rápida quando começar.

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