Write one-page product briefs to get buy-in before investing in full specs.
/product-brief-writer1-2 hrs → 10 min
Compared to doing it manually
/product-brief-writerType this in Claude to run the skill
A full PRD is overkill for getting initial buy-in. You need a one-page pitch.
/welcome/product-brief-writer in Claude to run the skill/one-pager-creatorCreate compelling one-page feature briefs that align stakeholders quickly.
/onboarding-flow-designerDesign onboarding flows that guide users to value quickly without being annoying.
/user-story-writerWrite clear user stories with acceptance criteria following the INVEST principles.
/technical-spec-writerWrite technical specifications with architecture, data models, and API designs.
A product brief is a short document that defines the scope and goals of a product initiative. It's longer than a one-pager but shorter than a PRD — typically 2-3 pages covering problem, goals, scope, and success metrics.
A brief defines what you're trying to achieve and why (strategic alignment). A PRD defines exactly what to build and how it should work (implementation detail). Briefs come first and inform PRDs.
The product manager, with input from stakeholders. The brief should reflect cross-functional alignment on goals and scope before detailed planning begins. Get sign-off before investing in PRD work.
Get all 70 skills running in a system that knows your company, product, and customers.
All 70 skills + your company context in one system.