Daily Standup Notes for Openclaw

Openclaw Skills turns a messy brain dump into a polished daily standup update with Yesterday, Today, and Blockers sections.

terrycarter1985
v1.0.0
Jul 30, 2026
0
359
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install daily-standup-notes

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install daily-standup-notes using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Daily Standup Notes?

Openclaw Skills for Daily Standup Notes helps you convert free-form updates, voice transcripts, bullet lists, or scattered chat into a clear standup format that is easy to scan and share. It structures raw work notes into three standard sections: Yesterday, Today, and Blockers.

This skill is designed to reduce status-reporting overhead, improve consistency across scrum updates, and preserve important details like names, ticket IDs, PR numbers, and links. Openclaw Skills also enforces concise formatting, duplicate merging, and tense-aware output so the result is immediately ready to paste into a team update or meeting note.

Daily Standup Notes Use Cases

  • Convert a messy end-of-day brain dump into a clean daily standup update.
  • Prepare a scrum update from chat messages, bullet notes, or transcript snippets.
  • Summarize what was completed yesterday, what is planned today, and what is blocked.
  • Normalize updates from multiple sources into a consistent team format.
  • Capture blockers clearly for faster follow-up and team communication.
  • Save recurring standup notes into dated files or weekly rollups for later review.

How Daily Standup Notes Works

  1. Ingest the user's raw status input, which may come from chat, bullets, or a voice transcript.
  2. Extract individual work items and classify each one into Yesterday, Today, or Blockers.
  3. Merge duplicates or near-duplicates so the final update stays compact and readable.
  4. Apply tense rules: use past tense for Yesterday, present/future tense for Today, and concise phrasing for Blockers.
  5. Preserve critical identifiers such as names, PR numbers, ticket IDs, and links exactly as written.
  6. If an item could reasonably fit Yesterday or Today, place it under Today and mark it with [continue].
  7. Output the final result as a markdown standup note with the standard three-section template.
  8. Optionally save the finished note to a dated file or append it to a weekly rollup for recurring use.

Daily Standup Notes Setup

  1. Install or enable the skill in your Openclaw Skills environment.
  2. Provide the raw standup input in any supported form, such as chat text, bullets, or transcript notes.
  3. If you want saved output, choose a destination path before generating the note.
  4. For recurring workflows, create a folder structure for dated standup files.
mkdir -p standup
# Example dated file naming convention
# standup/2025-01-15.md
  1. For weekly tracking, keep an append-only rollup file and add each day's output beneath the previous entry.
  2. When using the skill repeatedly, ask it to preserve IDs, links, and names verbatim for traceability.

Daily Standup Notes Data Schema & Taxonomy

Openclaw Skills organizes the output into a simple three-section markdown schema optimized for standup reporting.

Section Purpose Content Rules
Yesterday Completed work Past tense, concise bullets, merge duplicates
Today Planned work Present/future tense, use [continue] for ambiguous items
Blockers Obstacles Short bullets describing anything preventing progress

Output conventions

  • Headings are written as **Yesterday**, **Today**, and **Blockers**.
  • Each item is a one-line bullet whenever possible.
  • Long items may be split into sub-bullets for readability.
  • If a section has no entries, it should contain _None reported._
  • Names, PR numbers, ticket IDs, and links are preserved verbatim for auditability.

Suggested file taxonomy

  • standup/YYYY-MM-DD.md for daily notes
  • standup/week-YYYY-WW.md for weekly rollups
  • Optional metadata can be added in the filename or surrounding workflow, but the core skill output remains focused on the three-section markdown structure.

Daily Standup Notes Advanced Features

  • Supports multiple input formats, including free-form brain dumps, chat logs, bullet lists, and voice transcripts.
  • Automatically classifies content into Yesterday, Today, and Blockers to minimize manual editing.
  • Deduplicates repeated or near-identical items for cleaner executive-ready updates.
  • Preserves identifiers and links verbatim, which is useful for PR tracking, issue references, and team handoff.
  • Uses tense-aware rewriting and [continue] tagging to handle ambiguous status items consistently.
  • Can be paired with dated file saving or weekly rollup workflows for recurring Openclaw Skills usage.
  • Produces a standardized markdown template that works well in team communication and async status reporting.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*