brief

Summarize project status and team activity from dashboard briefs.

7|Updated Dec 1, 2025
One-click install
npx skills add https://github.com/Nate-Vish/Auto-Mates --skill brief-nate-vish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brief
Source: https://github.com/Nate-Vish/Auto-Mates/tree/main/.claude/skills/brief
Command: npx skills add https://github.com/Nate-Vish/Auto-Mates --skill brief-nate-vish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly surfaces a high-level view of project state, team activity, and outstanding requests by reading dashboard files to keep stakeholders aligned.

Core Features & Use Cases

  • Reads Dashboard/Brief.md to assemble the unified project brief (active projects, recent activity, next steps).
  • Scans Dashboard/Work_Space/ for KNOWLEDGE_REQUEST_*.md files to surface pending requests and ownership.
  • Outputs a concise, formatted project brief suitable for quick executive updates.

Quick Start

Invoke /brief to generate the current project brief.

Frequently Asked Questions about brief

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

FAQPage Schema
How do I generate a quick executive project status update from dashboard files?

To generate an executive project status update, the Skill reads Dashboard/Brief.md to assemble active projects, recent activity, and next steps into a concise, formatted project brief suitable for quick stakeholder alignment.

Can I surface pending knowledge requests and ownership from my workspace?

Yes, you can surface pending knowledge requests by scanning the Dashboard/Work_Space/ directory for KNOWLEDGE_REQUEST files, which extracts and displays pending requests along with their specific ownership details.

What is the best way to summarize team activity and project state for stakeholders?

The best way to summarize team activity and project state is to invoke the Skill, which operates across active projects and team status files to output a concise, formatted brief keeping stakeholders aligned.

Do I need specific dashboard file structures to summarize project status?

Yes, you need specific dashboard file structures: the Skill requires a Dashboard/Brief.md file to assemble the unified project brief and a Dashboard/Work_Space/ directory containing KNOWLEDGE_REQUEST files to function correctly.

How does tracking pending knowledge requests keep project teams aligned?

Tracking pending knowledge requests keeps teams aligned by scanning Dashboard/Work_Space/ for KNOWLEDGE_REQUEST files, surfacing outstanding requests and ownership so stakeholders can quickly address blockers via the formatted project brief.