create-brief

Interview users to create a quality-gated product brief with scope and metrics.

15|5|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/sohei56/maul-team --skill create-brief
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-brief
Source: https://github.com/sohei56/maul-team/tree/main/skills/create-brief
Command: npx skills add https://github.com/sohei56/maul-team --skill create-brief

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns an unclear product idea into a concise, decision-ready brief that gives human and autonomous teams a shared source of truth for scope, priorities, success, and trade-offs.

Core Features & Use Cases

  • Structured Interview: Co-author a 1–2 page brief through a focused conversation covering the problem, users, outcomes, scope, constraints, priorities, risks, and milestones.
  • Quality Gate: Identify vague metrics, missing non-goals, premature solutioning, unbounded scope, unmarked assumptions, and other gaps before the brief is finalized.
  • Safe Refinement: Read an existing brief, strengthen thin sections in place, and avoid overwriting documents that are already strong.
  • Use Case: When starting a new software project, use this Skill to clarify the target users, define falsifiable success metrics, establish what is explicitly out of scope, and save the result as the team's product brief.

Quick Start

Ask the create-brief skill to interview you about a new product idea and produce a quality-gated product brief.

Frequently Asked Questions about create-brief

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

FAQPage Schema
How do I create a product brief that defines clear scope and success metrics?

To create a product brief with clear scope and success metrics, participate in a structured interview that resolves ambiguous goals into a concise document covering falsifiable metrics, explicit non-goals, and constraints before saving.

What is the best way to refine an existing product brief that lacks measurable success criteria?

Refining an existing product brief requires a safe refinement process that reads the document and strengthens thin sections in place, adding measurable success criteria without overwriting sections that are already strong.

How does structured interviewing help with product discovery and scope definition?

Structured interviewing facilitates product discovery by co-authoring a focused brief through conversation, ensuring scope definition captures target users, priorities, risks, and milestones for aligned product work.

Can I use this approach to establish non-goals and prevent premature solutioning during product planning?

Yes, you can establish non-goals and prevent premature solutioning by applying a quality gate that identifies unbounded scope, missing non-goals, and vague metrics before finalizing the product brief.

Does product brief creation require human participation for autonomous software teams?

Product brief creation requires human participation even for autonomous software teams, as the process depends on structured interviewing and quality validation to produce a decision-ready source of truth.

When should I not use an interactive product-discovery ceremony for scope definition?

You should avoid an interactive product-discovery ceremony when you lack writable product documentation or cannot provide the human participation required for structured interviewing and quality validation.