skills.rest
LumenWipe
LumenWipeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

product-brief

Create, update, or validate product briefs with decision logs and addenda.

3|1|Updated May 12, 2026
Search Tags:#requirements#product strategy#decision logging#product brief#stakeholder alignment#product discovery#brief validation
One-click install
npx skills add https://github.com/LumenWipe/lumenwipe --skill product-brief-lumenwipe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-brief
Source: https://github.com/LumenWipe/lumenwipe/tree/main/.claude/skills/product-brief
Command: npx skills add https://github.com/LumenWipe/lumenwipe --skill product-brief-lumenwipe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill helps users turn incomplete product ideas, existing briefs, or change requests into focused, honest product briefs without inventing assumptions, padding the document, or losing important decisions.

Core Features & Use Cases

  • Brief Creation: Facilitate discovery, clarify the product problem, identify users and scope, and produce a right-sized brief.
  • Brief Updates: Reconcile existing briefs with new change signals while preserving context, conflicts, decisions, and rationale.
  • Brief Validation: Critique a brief against its intended purpose, cite specific weaknesses, and identify what cannot yet be evaluated.
  • Workflow Support: Resolve project customization, maintain decision logs and addenda, apply document standards, and prepare local or external handoffs.
  • Use Case: Use this Skill to pressure-test a Stellar account-closing product concept, distinguish confirmed facts from assumptions, and create a concise brief for product planning or stakeholder review.

Quick Start

Use the product-brief skill to create a concise product brief for the product idea and source materials I provide, calling out assumptions and open questions.

Frequently Asked Questions about product-brief

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

FAQPage Schema
How do I write a product brief that aligns stakeholders without padding it with assumptions?▼

To write a product brief without padding, use conversational discovery to clarify the product problem, identify users and scope, and distinguish confirmed facts from assumptions. This produces a right-sized brief that maintains stakeholder alignment without inventing details.

What is the best way to update an existing product brief when new change signals arrive?▼

Updating a product brief with new change signals requires reconciling the existing document while preserving context, conflicts, decisions, and rationale. This ensures the brief validation process maintains historical decision logging integrity without losing important context.

How do I validate a product brief to check if it is ready for stakeholder review?▼

Validating a product brief involves critiquing it against its intended purpose, citing specific weaknesses, and identifying what cannot yet be evaluated. This honest brief validation highlights open questions and distinguishes confirmed facts from unverified assumptions.

Can I use this approach for product discovery on a completely new product concept?▼

Yes, brief creation for new product concepts facilitates product discovery by clarifying the product problem, identifying users and scope, and producing a concise brief. It applies conversational discovery to pressure-test ideas before committing to product planning.

How do I maintain a decision log when revising product strategy and scope?▼

Maintaining a decision log during product strategy revisions requires applying document standards that record conflicts, decisions, and rationale as addenda. This preserves context during brief updates and supports accurate handoffs for stakeholder preparation.

Related Skills

Explore More Product & Management Skills→
AstrumonAstrumon

idea-brainstormer

Convert vague ideas into structured problem statements with feasibility assessments.

Community
Advanced
efekrbasefekrbas
41

design-orchestration

Route design work through brainstorming, review, and approval before implementation.

Community
Advanced
pisithrpspisithrps

decision-doc

Document product decisions with rationale, alternatives, and tradeoffs.

Community
Intermediate
harkersharkers

control-plane-agent

Coordinate multi-agent handoff workflows with verification gates and standardized handoff packets.

Community
Advanced