what-to-demo

Scan two weeks of daily notes and rank demo-worthy items.

5|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/tomzx/agents --skill what-to-demo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: what-to-demo
Source: https://github.com/tomzx/agents/tree/main/skills/what-to-demo
Command: npx skills add https://github.com/tomzx/agents --skill what-to-demo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the process of identifying a subset of two weeks' worth of notes that are suitable for demos, reducing manual sifting and ensuring visibility of user-facing improvements.

Core Features & Use Cases

  • Scans two weeks of daily notes to surface completed features, notable changes, and interesting work.
  • Ranks items by demo-worthiness based on impact, visibility, or novelty.
  • Generates a deterministic output file at the configured path for review: {BASE_DIR}/{YEAR}/{MONTH}/{DAY}.what-to-demo.md.

Quick Start

Run the skill to scan two weeks of notes and output a list of demo-worthy items.

Frequently Asked Questions about what-to-demo

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

FAQPage Schema
How do I find demo-worthy work from my daily notes?

To find demo-worthy work, this skill scans your past two weeks of daily notes, ranks completed features and notable changes by impact and visibility, and writes the results to a markdown file for review.

Can I automatically surface completed features for a sprint demo?

Yes, you can automatically surface completed features for a sprint demo by running this skill, which ranks items from your daily notes by demo-worthiness based on novelty and user-facing impact.

What do I need to set up before scanning notes for demo material?

Before scanning notes for demo material, you need to configure the NOTES_DIR environment variable and have at least one week of daily notes available, plus the scripts/get-env utility to resolve paths.

How does the ranking mechanism work for identifying demo-worthy items?

The ranking mechanism identifies demo-worthy items by scanning daily notes and evaluating completed features based on their impact, visibility, and novelty to determine their demo-worthiness.

Where does the generated demo-worthy output list get saved?

The generated demo-worthy output list is saved deterministically as a markdown file at the path {BASE_DIR}/{YEAR}/{MONTH}/{DAY}.what-to-demo.md for your review.