Create compelling one-page feature briefs that align stakeholders quickly.
2-3 hrs → 20 min
Compared to doing it manually
/one-pager-creatorType this in Claude to run the skill
Getting exec alignment takes forever. You either write too much (they don't read it) or too little (they ask questions you can't answer). The meeting goes sideways.
.claude/skills/ folder in your project/one-pager-creator in Claude to run the skillWrite one-page product briefs to get buy-in before investing in full specs.
Design onboarding flows that guide users to value quickly without being annoying.
Write clear user stories with acceptance criteria following the INVEST principles.
Write technical specifications with architecture, data models, and API designs.
A one-pager is a concise document (literally one page) that summarizes a product, feature, or initiative. It includes the problem, solution, key benefits, and next steps. It's designed to be skimmable and shareable.
One-pagers are for initial alignment and buy-in — before committing to build. PRDs come after alignment, adding detail for implementation. Think: one-pager for "should we?" and PRD for "how should we?"
Start with the headline (what and why). Then: problem, solution, key metrics, risks, and ask. Use bullets, not paragraphs. Include one visual if it helps. If it doesn't fit on one page, it's not a one-pager.
Download this skill and drop it in your .claude/skills/ folder.
This skill + 70+ more, context files, and agent workflows — $499