brief

Read docs/insights markdown files and enforce a pre-work briefing gate.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/mbriggsy/ai-learning-journey --skill brief-mbriggsy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brief
Source: https://github.com/mbriggsy/ai-learning-journey/tree/main/projects/skills/distill-and-brief/brief
Command: npx skills add https://github.com/mbriggsy/ai-learning-journey --skill brief-mbriggsy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Surfaces documented gotchas, root causes, and lessons from docs/insights before starting work to help teams avoid known landmines and repeat mistakes.

Core Features & Use Cases

  • Reads and surfaces insights from docs/insights/ to provide pre-task context for any component, phase, or subsystem.
  • Enforces a pre-work briefing gate, so the agent cannot proceed with work until a briefing is loaded.
  • Integrates documented lessons into the agent's reasoning context to reduce repeated issues.

Quick Start

Ask it to brief you on known issues and insights for the target component before you start.

Frequently Asked Questions about brief

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

FAQPage Schema
How do I surface known issues and gotchas before starting a development task?

To surface known issues before starting work, you can use a pre-task briefing that reads documented insights from your knowledge base and injects them into the agent context. This prevents repeating documented mistakes by ensuring documented root causes are loaded beforehand.

What is a pre-task briefing gate and how does it enforce context loading?

A pre-task briefing gate is a gating hook that blocks work commands until documented insights are loaded. It enforces context loading by reading knowledge base files at startup and preventing the agent from proceeding until the briefing is complete.

How do I load component insights and lessons from a markdown knowledge base into agent context?

You load component insights by dynamically reading markdown files from your docs/insights directory at startup. This process injects documented lessons and root causes directly into the agent's reasoning context to reduce repeated issues.

Can I block work execution until a pre-task briefing is reviewed?

Yes, you can block work execution until a briefing is reviewed by using a gating hook. This hook prevents work commands from executing until the documented insights and known landmines are fully loaded into the context.

What are the limitations of using markdown files for pre-task context and briefings?

Using markdown files for pre-task context requires maintaining a dedicated docs/insights directory. The briefing mechanism relies entirely on these files being present and accurate, meaning any undocumented issues will not be surfaced during the gating process.