product-brief

Create, update, and validate product briefs through conversational coaching and structured workflows.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/JHAMILCALI/Stellar-Build --skill product-brief-jhamilcali
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-brief
Source: https://github.com/JHAMILCALI/Stellar-Build/tree/main/.claude/skills/product-brief
Command: npx skills add https://github.com/JHAMILCALI/Stellar-Build --skill product-brief-jhamilcali

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Turning a rough product idea into a clear, honest, right-sized product brief is hard: assumptions go unexamined, context gets lost, and drafts drift out of sync with decisions. This Skill coaches you through creating, updating, or validating a brief so the output reflects your own thinking with rigor matched to your purpose. ## Core Features & Use Cases - Three intent modes: Create a new brief from scratch, Update an existing brief against a change signal, or Validate a brief with honest, line-cited critique. - Conversational discovery with coaching: Brain-dump friendly elicitation, web-research subagents for landscape grounding, and a choice between a Fast path (batched questions with [ASSUMPTION] tags) and a Coaching path (section-by-section pushback). - Persistent workspace and audit trail: Writes brief.md, addendum.md, and .decision-log.md to a run folder, supports resume across sessions, and applies configurable doc standards and external handoffs (e.g., Confluence) at finalize. - Use Case: A product manager pitching tomorrow invokes the skill, dumps their notes and a Slack thread, picks the Fast path, and receives a polished 1-2 page brief with assumptions flagged for review. ## Quick Start Ask the assistant to help you create a product brief for your idea and answer its discovery questions.

Frequently Asked Questions about product-brief

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

FAQPage Schema
How do I create a product brief with AI assistance?▼

Invoke the skill and describe your idea in a brain dump, including any source material like memos or transcripts. The skill runs a discovery conversation, offers a Fast path or Coaching path, then writes brief.md with YAML frontmatter to a run folder.

How to validate an existing product brief?▼

Use the Validate intent: the skill reads the brief, addendum, decision log, and original inputs, then returns an inline critique citing specific lines. It always offers to roll findings into an Update afterward.

Can I resume an unfinished product brief session?▼

Yes. The workspace persists on disk in a run folder containing brief.md, addendum.md, and .decision-log.md. If a prior in-progress draft exists for the project, the skill offers to resume it.

Does the product brief skill work in headless mode?▼

Yes. In headless mode it infers intent without prompting, completes the work from available inputs, and returns a JSON status block with artifact paths. If intent is ambiguous, it halts with a blocked status and reason.

What are the limitations of the generated product brief?▼

Briefs are intentionally scoped to 1-2 pages; deeper detail goes to addendum.md for downstream documents like PRDs. Validation caveats anything that cannot be evaluated, and the skill does not fabricate market sizing or moats.