daily-meeting

Automates engineering standup prep by collecting data from Git, tests, and Linear.

43|2|Updated Jan 25, 2024
One-click install
npx skills add https://github.com/glowingkitty/OpenMates --skill daily-meeting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daily-meeting
Source: https://github.com/glowingkitty/OpenMates/tree/main/.agents/skills/daily-meeting
Command: npx skills add https://github.com/glowingkitty/OpenMates --skill daily-meeting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It coordinates a consistent daily standup workflow by gathering repo, tests, infrastructure health, inspirations, legal/compliance signals, and Linear task context so your priorities are grounded in what actually changed.

Core Features & Use Cases

  • Step-by-step daily standup: Runs a structured conversation that reviews yesterday, assesses system health, and confirms priorities with the user.
  • Operational data gathering with fault tolerance: Pulls Git activity, test results, provider status, OpenObserve error counts, server stats, Linear issues, session quality, inspirations, compliance scan findings, and the prior meeting summary while continuing even when a single data source fails.
  • Priority and milestone actions: Labels up to 10 daily-priority tasks as Urgent, comments on the top 3 with rationale, updates milestones, saves meeting state, and writes a daily summary.

Quick Start

Ask: run the daily-meeting standup for today and, after you confirm priorities, apply the Linear label updates and milestone changes.

Frequently Asked Questions about daily-meeting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate daily standup preparation with Git activity and Linear issues?

Automating daily standup preparation involves gathering Git activity, test results, server health, and Linear issues to guide a step-by-step prioritization conversation grounded in actual system changes. This approach coordinates consistent daily operational workflows.

What is an evidence-based daily standup and how does it work?

An evidence-based daily standup reviews yesterday's progress, assesses current system health, and confirms priorities by collecting engineering signals from Git, tests, infrastructure, compliance scans, and task trackers. This mechanism grounds daily task selection in verified operational facts.

Can I run a dry-run daily standup to review priorities without updating Linear issues?

Yes, you can run a dry-run daily standup to review gathered system context and confirm priorities without applying updates. This mode allows you to evaluate suggested task selection before committing label or milestone changes to Linear.

Does daily standup automation work if the server monitoring or compliance scan data source fails?

Daily standup automation works even if server monitoring or compliance scan data sources fail by using parallel data gathering with explicit error handling. This fault tolerance ensures the prioritization conversation continues with available engineering signals.

How do I label daily priority tasks and update milestones for my engineering team?

You label daily priority tasks and update milestones by applying Urgent labels to up to 10 tasks, commenting on the top 3 with rationale, and updating Linear milestones. This action persists meeting state and writes a daily summary.