digest

Generates a daily CTO digest summarizing fleet health, recent ADRs, and pending escalations.

1|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/apireno/agent-workflow-template --skill digest-apireno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: digest
Source: https://github.com/apireno/agent-workflow-template/tree/main/.claude/skills/digest
Command: npx skills add https://github.com/apireno/agent-workflow-template --skill digest-apireno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering leaders running multi-repo agent workflows lack a single consolidated view of fleet health, recent architectural decisions, and items awaiting their attention, forcing them to manually inspect scattered files and inboxes each morning. ## Core Features & Use Cases - Fleet Health Check: Runs the preflight script and reports top-line status (ok, warnings, or critical) across all registered repos. - Decision Tracking: Lists ADRs and CTO decisions created in the last 7 days with timestamps and file sizes. - Escalation Surfacing: Counts and previews pending escalations in the ~/.cto/inbox directory. - Use Case: A solo developer acting as CTO starts the day by asking for the digest, receives a 5-line summary plus a dated markdown file at ~/cto-daily-YYYYMMDD.md, and immediately sees which escalations and sprint accepts need attention. ## Quick Start Ask the agent to generate today's CTO digest and summarize what needs my attention.

Frequently Asked Questions about digest

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

FAQPage Schema
How do I generate a daily engineering status digest across multiple repos?

Invoke the digest skill, which runs the fleet preflight script, scans docs/architecture/decisions for ADRs and CTO decisions from the last 7 days, and counts pending escalations in ~/.cto/inbox. It writes the result to ~/cto-daily-YYYYMMDD.md and returns a 5-line summary.

What data sources does the CTO digest aggregate?

It aggregates four sources: preflight.sh fleet health output, ADR-*.md files modified in the last 7 days, cto-decision-*.md files from the last 7 days, and markdown files in the ~/.cto/inbox escalation directory.

Can the digest skill run as a scheduled task?

Yes, the skill description notes it can be wired as a scheduled task in addition to manual invocation. It overwrites the same-day output file, so rerunning it within one day is safe.

What happens if the escalation inbox does not exist?

The digest reports that no inbox is configured when ~/.cto/inbox is missing, rather than failing. It notes this as pending Sprint B work and continues generating the rest of the digest.

Does the digest show per-repo sprint status?

No, detailed per-repo Phase 2 fleet state is delegated to the separate /sprint-status skill. The digest only references it and focuses on health, decisions, and escalations.