write-a-prd

仓库创建 2026年4月15日最近提交 20 天前SkillHot 收录 20 天前

▸ 精选理由

快速把模糊任务转为可执行需求，利于规划与评审。

这个 Skill 做什么

根据任务或意图生成结构化的产品需求文档（PRD）。

把任务描述或目标整理成一份结构化的产品需求文档（PRD），包含概述、问题陈述、目标、范围、功能、验收标准和指标。规划阶段或在协调执行前用来对齐需求，方便把大目标拆成可执行步骤。产出的重点是可验证的验收条件和度量，便于后续评审和验收。

▸ 展开 SKILL.md 英文原文

Generate a Product Requirements Document from a task description, user intent, or PRD outline. Structure the PRD with sections: Overview, Problem Statement, Goals, Scope, Features, Acceptance Criteria, Metrics. Use this when the Planner or Orchestrator needs to formalize requirements before decomposing into implementation steps.

内容创作产品需求结构化文档验收标准通用

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/Codebrew-company/CodebrewRouter/master/.agents/skills/write-a-prd/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/Codebrew-company/CodebrewRouter/master/.agents/skills/write-a-prd/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# Write a PRD — generate a Product Requirements Document

Formalizes task intent into a structured PRD that serves as input to the Planner or Orchestrator.

## When to use

- **Planner phase:** Before decomposing a task into steps, generate a PRD to align on requirements.
- **Orchestrator setup:** Before running the autonomous loop, generate/refine a PRD.
- **Specification clarity:** Task description is vague; PRD forces clarity on scope + acceptance criteria.

## Template

A PRD for Blaze.LlmGateway tasks typically has:

```markdown
# PRD: <Feature Name>

## Overview
<One-paragraph executive summary: what, why, who benefits>

## Problem Statement
<Current state, pain point, why it matters>

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有