rcode-product-brief

Create executive product briefs from raw ideas, notes, and supporting documents.

2|1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/hanzlahabib/rcode --skill rcode-product-brief
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rcode-product-brief
Source: https://github.com/hanzlahabib/rcode/tree/main/rcode/skills/actions/1-analysis/rcode-product-brief
Command: npx skills add https://github.com/hanzlahabib/rcode --skill rcode-product-brief

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns rough ideas, scattered notes, and existing research into a clear executive product brief, so teams can align on the problem, the audience, and the opportunity before committing to a larger PRD.

Core Features & Use Cases

  • Guided discovery: Helps the user clarify what they are briefing, even when the idea starts as a messy brain dump or multiple competing directions.
  • Context synthesis: Reviews relevant project documents, planning artifacts, and background material to capture useful details without forcing a rigid questionnaire.
  • Research-informed drafting: Produces a concise 1-2 page brief with problem, user, solution, success criteria, scope, and risk framing.
  • Review and refinement: Runs skeptical, opportunity, and contextual review passes to strengthen the brief before finalizing it.
  • Downstream planning support: Captures overflow details for an optional distillate that can feed later PRD creation or deeper planning.
  • Use case: A founder or product manager can hand over a concept, related docs, and rough goals, then receive a polished brief that is ready to share with stakeholders.

Quick Start

Ask the skill to create a product brief for your idea and share any notes, research, or draft documents you want it to use.

Frequently Asked Questions about rcode-product-brief

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

FAQPage Schema
How do I turn scattered product ideas and notes into an executive product brief?▼

To create an executive product brief from scattered notes, you need a context synthesis process that consolidates raw ideas, background documents, and research into a concise problem, user, and solution framing.

What is the best way to write a product brief for stakeholder alignment?▼

The best way to write a product brief for stakeholder alignment is through guided discovery and review-driven refinement, producing a 1-2 page summary of success criteria, scope, and risks.

Can I use market research to draft a product brief for an internal tool?▼

Yes, you can use market research to draft a product brief for an internal tool by applying research-informed drafting that captures relevant project documents and planning artifacts to define the opportunity.

How does context synthesis work when creating a product brief from messy brain dumps?▼

Context synthesis for product briefs works by reviewing messy brain dumps and competing directions without a rigid questionnaire, clarifying the core concept through staged context gathering and guided discovery.

Does writing a product brief require a full PRD before stakeholder alignment?▼

No, writing a product brief does not require a full PRD first; a concise executive brief captures overflow details in an optional distillate to feed downstream PRD creation and deeper planning.

When should I not use an executive product brief for my product concept?▼

You should not use an executive product brief when you need detailed technical specifications or exhaustive feature lists, as it focuses on high-level problem, audience, and opportunity framing rather than implementation details.