1 min read
Project Briefing Cadence
Project briefing turns recent commits and project activity into executive context, then promotes only durable project lessons.
project-briefing runs daily when configured. It pairs naturally with code-bugfix, which scans recent commits for likely bugs. Source: automations/project-briefing.md; automations/code-bugfix.md
Inputs
- repository commit history from the last 24 hours
- project agent docs when available
- linked issues, PRs, or status docs when referenced
- current project pages in the wiki
Durable Behavior
| Finding | Target |
|---|---|
| Project status, shipped capability, or strategic change | Project page or work summary. |
| Architecture or workflow lesson | Concept, workflow, decision, or postmortem page. |
| Repeated bug class | Skill, guardrail, or code-bugfix workflow update. |
| Routine commit list | Output-only briefing. |
Done
The briefing is done when it writes output, updates durable pages only when needed, updates automation state, and logs the run.
Timeline
- 2026-07-01 | Expanded project briefing into an inputs and durable-behavior runbook linked to code-bugfix and agent-docs. Source: User request, 2026-07-01
- 2026-05-31 | Project briefing cadence from HEARTBEAT daily table. Source: public wiki expansion, 2026-05-31