daily-vibe-update

Generate daily.md and todo.md reports from a plan and date.

18|9|Updated Apr 20, 2025
One-click install
npx skills add https://github.com/PHMbench/PHM-Vibench --skill daily-vibe-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daily-vibe-update
Source: https://github.com/PHMbench/PHM-Vibench/tree/main/.codex/skills/daily-vibe-update
Command: npx skills add https://github.com/PHMbench/PHM-Vibench --skill daily-vibe-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Daily Vibe Update addresses the tedium of manually compiling day-end summaries and tomorrow's tasks by automatically creating standardized daily.md and todo.md files, and by linking essential evidence paths for traceability.

Core Features & Use Cases

  • Automated Daily & Todo Creation: Generates <MM_DD>/codex/daily/daily.md and <MM_DD>/codex/todo/todo.md with consistent structure.
  • Deterministic Day Association: Ensures each day only produces one daily.md and one todo.md.
  • Evidence Linking: References key artifacts (report/manifest paths) in the Evidence section for auditability and traceability.
  • Plan-First Execution: Requires a brief plan before writing outputs to confirm Done/Blockers/Next/Evidence.
  • Template-Driven: Uses predefined daily and todo templates to standardize outputs across days.

Quick Start

Provide the target date in MM_DD format and topics for Evidence, then approve the generated plan to create daily.md and todo.md.

Frequently Asked Questions about daily-vibe-update

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

FAQPage Schema
How do I automate daily notes and task list generation in markdown?

Automate daily notes and task lists by generating standardized daily.md and todo.md files using predefined templates. You provide a target date and evidence topics, approve a brief execution plan, and the system writes consistent day-end summaries and next actions automatically.

What is the best way to track daily work evidence for traceability?

Track daily work evidence by referencing key artifact paths, such as reports and manifests, directly in the Evidence section of your daily.md. This mandatory linking ensures auditability and traceability for personal or team workflows without manual compilation.

How do I enforce consistent folder structures for daily reports?

Enforce consistent folder structures by using deterministic file paths for daily outputs. The automation assigns each day a specific directory, ensuring only one daily.md and one todo.md are produced per target date in a standardized location.

Do I need to write a plan before generating daily summaries?

Yes, a mandatory pre-write plan step is required before generating daily summaries. You must review and approve a brief outline of Done items, Blockers, Next actions, and Evidence references to confirm accuracy before the markdown files are written.

Can I use template-driven daily reports for team workflows?

Template-driven daily reports apply to both personal and team workflows where consistent day-end summaries are required. The standardized templates ensure uniform structure across all team members, capturing next actions and evidence uniformly.

What are the limitations of automating todo.md and daily.md creation?

Limitations include strict reliance on MM_DD date formats and predefined templates, meaning custom file structures or non-standard naming conventions are not supported. The automation enforces deterministic paths, limiting flexible file placement.