heartbeat-standup
Skill4 starsChanged 4 months agoMITView on GitHub
Scheduled daily standup for every Paperclip agent — each weekday evening, post shipped / in-progress / blocked / budget / tomorrow's plan as a formatted comment in the Paperclip ticket UI. Use on the daily standup heartbeat, or when asked to "post my standup", "daily update", "end-of-day report", or "what did you get done today". Don't use for escalating urgent blockers (delegation-protocol, the moment it happens) or budget warnings (budget-guardrails).
In this repository74 other files it gives its agents.
- agent-eval-harnessSkill
- context-budget-managerSkill
- incident-rollbackSkill
- memory-hygieneSkill
- model-cost-optimizerSkill
- prompt-debuggerSkill
- skill-author-coachSkill
- third-party-skill-vetterSkill
- api-endpoint-testerSkill
- bug-triage-protocolSkill
- changelog-release-notesSkill
- docs-readme-writerSkill
- env-secrets-hygieneSkill
- github-pr-reviewSkill
- git-ship-flowSkill
- lovable-brief-writerSkill
- supabase-migration-writerSkill
- vercel-deploy-checkSkill
- cold-outreach-sequencerSkill
- competitor-pricing-scanSkill
- contract-redline-scanSkill
- customer-support-inboxSkill
- invoice-runnerSkill
- kpi-dashboard-weeklySkill
- lead-research-dossierSkill
- payment-reconciliationSkill
- pipeline-trackerSkill
- proposal-builderSkill
- stripe-payment-linkSkill
- testimonial-harvesterSkill
- weekly-revenue-reportSkill
- brand-voice-guardianSkill
- case-study-builderSkill
- content-repurposerSkill
- deep-research-briefSkill
- email-nurture-sequenceSkill
- landing-page-copywriterSkill
- linkedin-content-packSkill
- newsletter-assemblerSkill
- seo-blog-writerSkill
- social-listening-reportSkill
- x-thread-builderSkill
- youtube-script-writerSkill
- budget-guardrailsSkill
- ceo-operating-doctrineSkill
- delegation-protocolSkill
- editor-personaSkill
- hiring-briefSkill
- ops-agent-personaSkill
- researcher-personaSkill
- sales-agent-personaSkill
- support-agent-personaSkill
- weekly-retroSkill
- writer-personaSkill
- calendar-conciergeSkill
- decision-journalSkill
- email-triageSkill
- file-organizerSkill
- habit-trackerSkill
- inbox-zero-sprintSkill
- The first 60 shown.
The file
Files
Heartbeat Standup
The 6 p.m. weekday ritual for every agent in the org, CEO included. One formatted comment that lets a human skim the whole team in two minutes: what shipped, what's moving, what's stuck, what it cost, what's next. The standard: every line traces to a ticket ID, every number is real, and "blocked" always names who unblocks it.
When to Use
- The standup heartbeat fires (weekdays 18:00) — this is the default trigger.
- A human or the CEO asks for a daily update or end-of-day report.
- Not for: escalating an urgent blocker (do that the moment it happens via
delegation-protocol— standup only recaps it), budget warnings (fire those immediately perbudget-guardrails), or planning tomorrow's actual work (CEO'sceo-operating-doctrineheartbeat does that; your "tomorrow" section is intent, not assignment).
Role Boundary
- You own: an honest, complete standup of your own tickets, posted on time in the right place.
- You escalate: nothing new via standup — blockers listed here must already have been raised on their tickets. If you discover an unraised blocker while writing the standup, raise it on its ticket first, then list it.
- You never: report another agent's work as your own, mark something "shipped" that wasn't accepted per its definition of done, or skip the budget line.
Quick Reference
| Section | Rule |
| Shipped today | Only tickets accepted/closed today, with ticket IDs. Empty is a valid answer. |
| In progress | Ticket ID + one-line state + % or next milestone. No vague "working on it". |
| Blocked | Ticket ID + what's needed + who unblocks it + since when |
| Budget | Spent this month / cap / % — pulled fresh, not remembered |
| Tomorrow | Max 3 items, each tied to a ticket, in priority order |
| Where to post | Your standup thread/ticket in Paperclip so the CEO and humans see it in the ticket UI |
Procedure
- Pull the facts — list your tickets changed today (closed, commented, state-changed) and fetch fresh budget numbers per
budget-guardrails. Success: every claim you're about to make has a ticket ID or a number behind it. - Classify — sort into shipped (accepted today), in progress (open with movement or planned movement), blocked (waiting on someone/something — confirm each blocker was already raised on its ticket; if not, raise it there now).
- Check ancestry — for shipped and tomorrow items, note the project each ticket serves. If a ticket serves nothing, flag it in the standup ("orphan — needs a home or a close") rather than hiding it.
- Fill the template exactly — no section skipped; use "None" rather than omitting. Keep the whole post skimmable: aim under 20 lines, plain markdown that renders in the Paperclip ticket UI (headers, dashes, no tables-in-tables, no images).
- Post — as a comment on your standup ticket/thread. Success: it appears in the ticket UI, timestamped today.
- Cross-link — if your budget is ≥80% or a blocker is >48h old, @-mention the CEO on those specific lines so the standup doubles as a nudge, not a surprise.
Output Template
## Standup — {agent name} — {YYYY-MM-DD}
**Shipped today**
- {T-##} {title} — accepted ({project})
- None
**In progress**
- {T-##} {title} — {state, e.g. "draft v2 with editor, revision due tomorrow"}
**Blocked**
- {T-##} {what's needed} — waiting on {who} since {date}
- None
**Budget:** {spent} / {cap} ({%}) — {ok | ⚠ warning mode | ⛔ hard stop}
**Tomorrow (priority order)**
1. {T-##} {intent}
2. {T-##} {intent}Pitfalls
- The optimistic "shipped" — listing a draft delivered but not yet accepted as shipped; the CEO plans on top of work that bounces back. Recovery: shipped means accepted against the definition of done; move anything else to "In progress" with its true state, and correct yesterday's standup with a follow-up comment if you already misreported.
- Blocker debut at standup — a blocker appears in the standup that was never raised on its ticket, losing hours or a whole day. Recovery: raise it on the ticket immediately (with who unblocks it), then reference it in the standup; blockers are raised in real time, recapped at 18:00.
- Stale budget line — copying yesterday's number and drifting past 80% unnoticed. Recovery: the budget line must come from a fresh check at post time; if the fresh number crosses a threshold, trigger
budget-guardrailswarning behavior before posting. - The essay standup — 60 lines nobody reads, burying the one blocked item that mattered. Recovery: enforce the template's shape — one line per item, max 3 tomorrow items; details live on the tickets, the standup links to them.
Verification
- Posted to the standup thread/ticket, visible in the Paperclip ticket UI, dated today
- Every item carries a ticket ID; shipped items were actually accepted today
- Every blocker names who unblocks it and was already raised on its own ticket
- Budget line is freshly pulled; threshold crossings triggered
budget-guardrailsbehavior - All five sections present ("None" where empty); post is under ~20 lines
- CEO @-mentioned on any ≥80% budget or >48h blocker lines
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
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.

