daily-standup

Generates daily standup logs from PLAN.md and MVP-SPEC.md context.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/ComputerConnection/z-combinator --skill daily-standup-computerconnection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daily-standup
Source: https://github.com/ComputerConnection/z-combinator/tree/main/skills/daily-standup
Command: npx skills add https://github.com/ComputerConnection/z-combinator --skill daily-standup-computerconnection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Daily standups provide a ruthless, structured way to confirm progress, surface blockers, and track runway so teams stay aligned during the build phase.

Core Features & Use Cases

  • Phase-driven daily health checks that read PLAN.md and MVP-SPEC.md for context.
  • Automatic logging to STANDUP-LOG.md with shipped work, planned work, blockers, and runway status.
  • Quick prompts to maintain scope discipline and accelerate decisions.

Quick Start

Run the daily standup for today and append the results to STANDUP-LOG.md.

Frequently Asked Questions about daily-standup

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

FAQPage Schema
How do I automate daily standup logging for shipped features and blockers?

Automate daily standup logging by generating a formatted entry that tracks shipped features, planned work, blockers, and runway burn, then appending the results directly to STANDUP-LOG.md.

What is the best way to track runway burn during a build phase sprint?

Track runway burn during a build phase by enforcing daily health checks that read project context and append runway status updates to a central standup log file.

Do I need PLAN.md and MVP-SPEC.md files to run a daily progress check?

Yes, the daily progress check reads PLAN.md and MVP-SPEC.md to gather project context, ensuring the generated standup log accurately reflects current scope and planned work.

How does automated standup logging maintain scope discipline for quick course corrections?

Automated standup logging maintains scope discipline by using quick prompts to surface blockers and confirm progress, enabling fast decisions and visibility during the build phase.

Can I use this daily standup tracker for tasks outside of the build phase?

This daily standup tracker is specifically designed for build phase contexts, reading MVP specifications to enforce discipline and visibility rather than general project management tasks.