daily

Parse standup inputs and create daily notes with blockers and decisions.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ThuHuynh1438/pm-kit --skill daily-thuhuynh1438
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daily
Source: https://github.com/ThuHuynh1438/pm-kit/tree/main/.claude/skills/daily
Command: npx skills add https://github.com/ThuHuynh1438/pm-kit --skill daily-thuhuynh1438

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standup updates across multiple projects are often scattered and manual to compile. This Skill automatically captures daily progress, detects blockers and decisions, and creates centralized daily notes per day.

Core Features & Use Cases

  • Auto-parse standup input to extract per-project status (Shipped, WIP, Blocked) and identify blockers and decisions.
  • Create or update daily notes in a single daily file and update project indices and vault logs for traceability.
  • Use in multi-project teams to keep a single source of truth and accelerate standups with deterministic note creation.

Quick Start

Submit your standup update to Claude to generate today’s daily note for all projects and log any blockers or decisions detected.

Frequently Asked Questions about daily

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

FAQPage Schema
How do I automate daily standup notes across multiple projects?

Automating daily standup notes across multiple projects involves parsing standup inputs to classify items as Shipped, WIP, or Blocked, then generating a centralized daily note. This process automatically detects blockers and decisions, updating project indices and vault logs for full traceability.

What is the best way to track blockers and decisions from multi-project standups?

Tracking blockers and decisions from multi-project standups is best handled by auto-detecting them from parsed status inputs. The system extracts per-project progress and generates dedicated blocker and decision notes within a single daily file, ensuring a single source of truth.

How do I compile a single source of truth for multi-project daily status updates?

Compiling a single source of truth for multi-project daily status updates requires logging parsed standup inputs into a centralized daily file. This approach automatically classifies shipped, WIP, and blocked items while updating project indices and vault logs for deterministic traceability.

Can I use automated daily reporting for multi-project teams to log shipped and WIP items?

Yes, automated daily reporting for multi-project teams can log shipped and WIP items. The system parses your standup input, classifies progress per project, and creates deterministic daily notes while indexing projects and logging vault updates for traceability.

Does daily note generation work without manual formatting for standup inputs?

Daily note generation works without manual formatting by parsing raw standup inputs directly. It automatically extracts per-project status, identifies blockers and decisions, and generates or updates a centralized daily file with deterministic note creation and context loading.