brief

Convert feature ideas into a locked BRIEF.md with scope and approval gate.

123|22|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/AlexZio00/claude-code-skills --skill brief-alexzio00
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brief
Source: https://github.com/AlexZio00/claude-code-skills/tree/main/brief
Command: npx skills add https://github.com/AlexZio00/claude-code-skills --skill brief-alexzio00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Locks a feature scope before code is written by converting initial ideas into a locked brief that defines what will be built, what won't, and how success is measured.

Core Features & Use Cases

  • Generates a structured Brief from user input, clarifying boundaries and acceptance criteria.
  • Enforces an approval gate before saving BRIEF.md.
  • Supports iterative revisions within a single session and clear scope boundaries (Scope IN/Scope OUT).

Quick Start

Provide a feature idea and I will generate a structured Brief with Scope IN/OUT and an approval gate.

Frequently Asked Questions about brief

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

FAQPage Schema
How do I lock feature scope before coding starts?

To lock feature scope before coding, you convert your initial idea into a structured brief that explicitly defines Scope IN, Scope OUT, acceptance criteria, and an approval gate. This prevents uncontrolled changes during implementation.

What is a project brief used for in workflow governance?

A project brief is used in workflow governance to establish a locked, implementation-ready scope before development. It defines exact boundaries and how success is measured, serving as an approval gate for BRIEF.md handoff.

How do I create an implementation-ready brief from a feature idea?

You create an implementation-ready brief by providing a feature idea to generate a structured document. The brief clarifies boundaries with Scope IN/OUT sections and enforces an approval gate before the final file is saved.

Can I revise a locked brief within a single session?

Yes, you can revise a brief within a single session. The workflow supports iterative revisions to clarify scope boundaries and acceptance criteria before the final approval gate is enforced for the BRIEF.md handoff.

What's the best way to define Scope IN and Scope OUT for a specification?

The best way to define Scope IN and Scope OUT is by generating a structured specification that explicitly separates what will be built from what won't. This enforces clear boundaries and establishes how success is measured.

Does a feature brief require an approval gate before saving?

Yes, a feature brief requires an approval gate before saving as BRIEF.md. This ensures the scope boundaries and acceptance criteria are locked and confirmed before any code is written.