daily-briefing

Scan project artifacts, debriefs, and git history to generate a daily briefing file.

2|1|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/msieurthenardier/mission-control --skill daily-briefing-msieurthenardier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daily-briefing
Source: https://github.com/msieurthenardier/mission-control/tree/main/.claude/skills/daily-briefing
Command: npx skills add https://github.com/msieurthenardier/mission-control --skill daily-briefing-msieurthenardier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate a daily, cross-project health snapshot by reading artifacts, debriefs, and recent git activity to surface status and momentum for multiple projects.

Core Features & Use Cases

  • Automated daily briefing across registered projects, surfacing health status, staleness signals, and actionable insights.
  • Artifact-driven analysis: reads missions, flights, legs, and debriefs to summarize progress and momentum.
  • Cross-project insights: aggregates learnings to identify patterns and improvement opportunities for methodology and workflows.

Quick Start

Review all registered projects, choose which to include in today’s briefing, and run the skill to generate daily-briefings/YYYY-MM-DD.md.

Frequently Asked Questions about daily-briefing

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

FAQPage Schema
How do I generate a daily project health briefing across multiple repositories?

A cross-project health briefing summarizes activity and staleness signals across multiple projects by scanning artifacts, debriefs, and recent git commits. It aggregates missions, flights, and legs to surface momentum and actionable insights.

How do I automate cross-project status reporting from git history and artifacts?

Automate cross-project reporting by scanning registered projects' artifacts, debriefs, and git logs to produce a daily briefing file. The scan reads ARTIFACTS.md, missions, flights, and recent commits without modifying any project files.

Can I select specific projects to include in my daily debrief scan?

Yes, you can optionally select specific registered projects to include in the daily briefing. The scan applies across all registered projects by default but allows targeted selection before generating the daily summary file.

Does the daily briefing scan modify my project files during analysis?

No, the daily briefing scan does not modify any project files. It strictly reads ARTIFACTS.md, missions, flights, legs, debriefs, and git logs, only generating a new daily-briefings/YYYY-MM-DD.md file.

What's the best way to identify cross-project insights and workflow patterns from recent commits?

Aggregate learnings from artifact-driven analysis and recent git activity across projects to identify cross-project insights. Scanning debriefs and commits surfaces workflow patterns and methodology improvement opportunities.