brief-spec

Ask targeted questions to capture acceptance criteria and generate a draft brief.

3|1|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/metraton/gaia --skill brief-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brief-spec
Source: https://github.com/metraton/gaia/tree/main/skills/brief-spec
Command: npx skills add https://github.com/metraton/gaia --skill brief-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conversational brief creation. The orchestrator loads this inline to co-create a brief with the user before dispatching to gaia-planner.

Core Features & Use Cases

  • Interactive brief creation: asks targeted questions to surface requirements and acceptance criteria.
  • Draft generation: writes a ready-to-review brief.md at the specified path for stakeholder alignment.
  • Hand-off readiness: produces a clean plan for gaia-planner to convert into a concrete feature plan.

Quick Start

Ask targeted questions to capture all acceptance criteria details, then create open_brief-spec/brief.md at .claude/project-context/briefs/open_brief-spec/brief.md.

Frequently Asked Questions about brief-spec

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

FAQPage Schema
How do I draft a feature brief before detailed planning?

To draft a feature brief, this Skill asks targeted questions to identify missing requirements and acceptance criteria, then generates a review-ready brief.md file for stakeholder validation.

What is the best way to capture acceptance criteria for a feature spec?

Capturing acceptance criteria for a feature spec is done through an interactive process where targeted questions surface missing requirements, ensuring all details are recorded before generating a draft brief.

How do I create a feature brief that works with gaia-planner?

Creating a feature brief for gaia-planner involves answering questions to define acceptance criteria, producing a clean draft brief.md that coordinates with gaia-planner to convert it into a concrete feature plan.

Does brief-spec work without external dependencies?

Yes, brief-spec operates without external dependencies, using an inline conversational process to co-create a brief and save it directly to the .claude/project-context/briefs/open_brief-spec/brief.md path.

Where does the generated feature brief get saved?

The generated feature brief is saved as a brief.md file at the .claude/project-context/briefs/open_brief-spec/brief.md path, ready for stakeholder alignment and validation before planning proceeds.

When should I use conversational brief creation over writing a spec manually?

Use conversational brief creation when you need to surface hidden requirements and define acceptance criteria through guided questions, ensuring a structured draft is ready for orchestrator dispatch and planning hand-off.