brief

Synthesize Slack, Linear, GitHub, and GDocs signals into daily or weekly briefs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/namankumar/product-os --skill brief-namankumar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brief
Source: https://github.com/namankumar/product-os/tree/main/.claude/skills/brief
Command: npx skills add https://github.com/namankumar/product-os --skill brief-namankumar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Daily or weekly briefing processes are error-prone and time-consuming when collating signals from many sources. This skill automates the synthesis into a single, consistent brief.

Core Features & Use Cases

  • Cross-source signal aggregation from Slack, Linear, GitHub, GDocs, and caches to produce a final brief.
  • Phase-based workflow: a refresh phase to gather data and an Agent D cross-referencing phase to unlock insights, followed by delivery to cache/brief files.
  • Automatic output of daily briefs and weekly briefs with appropriate context updates and optional comms drafting for stakeholders.

Quick Start

Trigger the daily briefing workflow with /daily-brief to generate cache/brief/brief-[YYYY-MM-DD].md.

Frequently Asked Questions about brief

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

FAQPage Schema
How do I automate daily briefs from Slack, Linear, and GitHub signals?

You can automate daily briefs by synthesizing cross-source signals from Slack, Linear, GitHub, and GDocs into a single narrative. Triggering the workflow generates a consolidated, decision-ready summary file for cross-functional teams.

What is cross-source signal synthesis for cross-functional team updates?

Cross-source signal synthesis aggregates data from platforms like Slack, Linear, and GDocs into one consistent brief. It resolves the time-consuming, error-prone process of manually collating updates across disparate caches.

How do I generate a weekly briefing with cross-referenced planning insights?

Generating a weekly briefing uses a two-phase flow: a refresh phase to gather data and an Agent D cross-referencing phase to unlock insights. Outputs are written to cache files for cadence-aware planning.

Does automated briefing work with GDocs and Linear caches for stakeholder comms?

Automated briefing works with GDocs, Linear, and other caches to produce summaries. It writes outputs to context files and can optionally draft comms for stakeholders, ensuring timely, decision-ready updates.

What is the best way to consolidate cross-functional team signals into one narrative?

The best way to consolidate signals is using an automated two-phase workflow that refreshes data and cross-references insights. This synthesizes Slack and GitHub updates into a single, consistent narrative brief.

Are there limitations to automated briefing for cadence-aware planning?

Automated briefing limitations depend on the availability of signals from connected caches like Slack, Linear, and GitHub. It is designed for daily or weekly cadences, so real-time updates outside these cycles may not be reflected.