brief

Generate and refine project briefs in `brief.md` format.

5|Updated Oct 22, 2025
One-click install
npx skills add https://github.com/marchatton/agent-skills --skill brief-marchatton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brief
Source: https://github.com/marchatton/agent-skills/tree/main/.agents/skills/02-shape/brief
Command: npx skills add https://github.com/marchatton/agent-skills --skill brief-marchatton

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you create or update a brief.md file, essential for clearly defining project or feature scope, goals, and potential issues.

Core Features & Use Cases

  • Project Scoping: Define clear goals, non-goals, and scope for new projects or features.
  • Risk Identification: Document top risks, unknowns, and open questions.
  • Use Case: When starting a new feature development, use this Skill to quickly draft a one-page brief that aligns stakeholders on the problem, desired outcomes, and boundaries.

Quick Start

Use the brief skill to create a new project brief based on the provided problem statement.

Frequently Asked Questions about brief

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

FAQPage Schema
How do I write a project brief for feature development?

To write a project brief, define the problem statement, set clear success metrics, outline scope, and identify top risks. A structured brief aligns stakeholders by clarifying goals, non-goals, and boundaries before development begins.

What is project shaping and when do I need a brief?

Project shaping is defining project scope, goals, and risks before development. You need a brief when starting new feature development to establish clear problem definition, desired outcomes, and boundaries for stakeholder alignment.

How do I define project scope and non-goals in a brief?

Define project scope and non-goals in a brief by explicitly documenting what the feature will and will not address. This structured project definition ensures stakeholders understand boundaries and prevents scope creep during development.

Can I iteratively refine a project definition with open questions?

Yes, you can iteratively refine a project definition through clarification questions. The brief supports updating scope and risk assessment by addressing unknowns and open questions as project details evolve during shaping.

Does this work for risk identification and documenting unknowns?

Yes, this works for risk identification by documenting top risks, unknowns, and open questions. The brief format provides a dedicated section to capture potential issues and risk assessment during project scoping.

What format does the generated project brief use?

The generated project brief uses the brief.md markdown format. This structured output includes sections for problem definition, success metrics, scope, non-goals, and risk assessment to align stakeholders on feature development.