Token导航 LogoToken导航TokenDH.com
待分类只读github未标认证来源可访问许可证需确认审计通过

writing-prds写 prd

Agent Skill

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

总安装

38,016

周安装

1,567

GitHub Stars

734

下载量

13,312
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:writing-prds(写 prd)
来源仓库:https://github.com/refoundai/lenny-skills
仓库路径:skills/writing-prds
安装命令:
npx skills add https://github.com/refoundai/lenny-skills --skill writing-prds
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/refoundai/lenny-skills --skill writing-prds

简介

使用 11 位产品负责人的框架帮助团队编写重点突出、可操作的产品需求文档。

  • 先从问题和背景开始,然后再提出解决方案;包括“为什么现在”,以证明时机和紧迫性与竞争优先事项的合理性
  • 为您的产品类型选择正确的格式:用于功能规格的传统 PRD、用于 AI 功能的原型或提示集、作为生活需求的可执行评估
  • 通过明确的指标和结果预先定义成功;保持文件轻量级并以结果为中心,而不是详尽无遗
  • 使用 PR/FAQ 格式以事实语言描述客户、问题和解决方案;考虑使用 AI 脚手架来处理用户故事和超出范围的项目等基础知识

SKILL.md

Writing PRDs

Help the user write effective product requirements documents using frameworks and insights from 11 product leaders.

How to Help

When the user asks for help with PRDs:

  1. Start with the why - Ask about the problem being solved and why it matters now, before features
  2. Define success upfront - Help them articulate how they'll know the feature succeeded
  3. Choose the right format - Discuss whether they need a traditional doc, a prototype, or executable evals
  4. Keep it actionable - Ensure the document leads to clear team action, not just documentation

Core Principles

Lead with problem and context

Maggie Crowley: "The most important section is the first part - what is the background and context? What is the problem, why does it matter, and why does it matter now?" Center the team on the 'why' and the urgency before discussing solutions.

The PR/FAQ forces clarity

Bill Carr: "Whenever we're devising a new product, we start by writing a press release describing it in a way that speaks to the customer. The idea better jump off the page." Use the PR to describe customer, problem, and solution in factual, data-rich language.

Demos before memos in AI age

Aparna Chennapragada: "If you're not prototyping and building to see what you want to build, you're doing it wrong. Prompt sets are the new PRDs." For AI features, include functional prototypes and prompt sets as core requirements.

Evals as living PRDs

Hamel Husain & Shreya Shankar: "This is the purest sense of what a product requirements document should be - this eval judge that's telling you exactly what it should be, and it's automatic and running constantly." Translate product requirements into executable evaluations for AI products.

Keep it lightweight for action

Eric Simons: "We tend to keep them pretty light. I like to have the minimal amount of context that ensures everyone's on the same page and that key outcomes will be present when we get there." Focus on key outcomes rather than exhaustive details that developers ignore.

PRDs demonstrate craft

Vikrama Dhiman: "Is your PRD quality good enough? Are you writing drafts that go to care teams, marketing teams? You must have impact through the artifacts you work on." High-quality PRDs demonstrate professional craft and create clarity at scale.

AI can scaffold the basics

Claire Vo: "I had used ChatGPT to come up with a very serviceable PRD spec for this very technical product." Use AI to scaffold basics like user stories and out-of-scope items, then focus on high-level strategy and narrative.

Live PRDs reduce ambiguity

Guillermo Rauch: "The product management team is now actually building the product. We've specced out in v0, think of it as a live PRD. The amount of detail - we're all saying 'just ship it.'" Interactive, animated prototypes reduce ambiguity and speed up approval.

Include the 'Why Now'

Justify the timing of this investment against other opportunities. If you can't explain why this matters now versus later, the priority is questionable.

Questions to Help Users

  • "What problem is this solving, and why does it matter now?"
  • "How will you know if this feature was successful - what metric moves?"
  • "Who is the customer, and what does their life look like after this ships?"
  • "What is explicitly out of scope to prevent scope creep?"
  • "Could you build a quick prototype instead of writing more documentation?"
  • "What are the key decisions that still need to be made?"

Common Mistakes to Flag

  • Starting with the solution - The document should lead with the problem and context
  • No success criteria - Every PRD needs a clear definition of how you'll measure success
  • Exhaustive detail - Lightweight PRDs focused on outcomes are more likely to be read and used
  • Static when prototypes work better - For AI and UI work, live prototypes communicate more than prose
  • Missing the 'Why Now' - Without urgency justification, priorities will be questioned

Deep Dive

For all 14 insights from 11 guests, see references/guest-insights.md

Related Skills

  • Writing Specs & Designs
  • Working Backwards
  • Stakeholder Alignment
  • Shipping Products

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

33.98%
按下载量换算4,523

Claude

32.99%
按下载量换算4,392

Cursor

17.82%
按下载量换算2,372

Gemini CLI

9.71%
按下载量换算1,293

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills