How do I install the Brief skill?

Run npx skillmds add majiayu000/brief in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Brief safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Brief?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Brief free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Brief by majiayu000 — Agent Skill

Name: Brief
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

/brief

Create or improve project brief through conversational discovery.

Usage

/brief                           # Interactive discovery for current or new project
/brief --project coordinatr      # Brief for specific project
/brief --review                  # Analyze existing brief (no edits)
/brief --force                   # Start from scratch

Output Location

ideas/[project]/project-brief.md

Execution Flow

1. Determine Mode

No brief exists -> Full Discovery Mode
Brief exists, no flags -> Gap-driven update mode
--review flag -> Analysis mode (no edits)
--force flag -> Fresh start (after confirmation)

2. Invoke brief-strategist Agent

For discovery, conduct 6-phase interactive conversation (one question at a time).

3. Six-Phase Discovery Topics

Problem Discovery - What problem? Who experiences it? Current solutions?
Solution Exploration - How does your solution work? Core value proposition?
Audience Definition - Who exactly is the target user? Characteristics?
Feature Prioritization - MVP features? What can wait?
Differentiation - What makes this different from alternatives?
Success Metrics - How will you measure success?

Brief Structure

---
status: draft | active | paused | archived
created: YYYY-MM-DD
updated: YYYY-MM-DD
---

# Project Brief: [Project Name]

## Executive Summary
[One-paragraph overview]

## Problem Statement
[Detailed problem description and impact]

## Solution Approach
[How the solution addresses the problem]

## Target Audience
[Specific user personas and characteristics]

## Success Criteria
[Measurable outcomes and validation metrics]

## Scope and Constraints
[Project boundaries and limitations]

## Project Phases
[High-level implementation roadmap]

## Risk Assessment
[Key risks and mitigation strategies]

When to Use

Starting a new idea
Revisiting an idea after time away
Before creating specifications
When vision feels unclear

Not needed for: Quick notes (use notes/), technical research (/research), feature details (/spec)

Next Steps After Brief

/brief -> /critique -> /research -> /spec -> /plan

---name: briefdescription: Create or update project brief through interactive discovery. Use when starting any new idea, revisiting an idea after time away, or when vision feels unclear.--- # /brief Create or improve project brief through conversational discovery. ## Usage ```bash /brief # Interactive discovery for current or new project /brief --project coordinatr # Brief for specific project /brief --review # Analyze existing brief (no edits) /brief --force # Start from scratch ``` ## Output Location ``` ideas/[project]/project-brief.md ``` ## Execution Flow ### 1. Determine Mode - **No brief exists** -> Full Discovery Mode - **Brief exists, no flags** -> Gap-driven update mode - **`--review` flag** -> Analysis mode (no edits) - **`--force` flag** -> Fresh start (after confirmation) ### 2. Invoke brief-strategist Agent For discovery, conduct 6-phase interactive conversation (one question at a time). ### 3. Six-Phase Discovery Topics 1. **Problem Discovery** - What problem? Who experiences it? Current solutions? 2. **Solution Exploration** - How does your solution work? Core value proposition? 3. **Audience Definition** - Who exactly is the target user? Characteristics? 4. **Feature Prioritization** - MVP features? What can wait? 5. **Differentiation** - What makes this different from alternatives? 6. **Success Metrics** - How will you measure success? ## Brief Structure ```markdown --- status: draft | active | paused | archived created: YYYY-MM-DD updated: YYYY-MM-DD --- # Project Brief: [Project Name] ## Executive Summary [One-paragraph overview] ## Problem Statement [Detailed problem description and impact] ## Solution Approach [How the solution addresses the problem] ## Target Audience [Specific user personas and characteristics] ## Success Criteria [Measurable outcomes and validation metrics] ## Scope and Constraints [Project boundaries and limitations] ## Project Phases [High-level implementation roadmap] ## Risk Assessment [Key risks and mitigation strategies] ``` ## When to Use - Starting a new idea - Revisiting an idea after time away - Before creating specifications - When vision feels unclear **Not needed for**: Quick notes (use notes/), technical research (/research), feature details (/spec) ## Next Steps After Brief ``` /brief -> /critique -> /research -> /spec -> /plan ```

Frequently asked questions