to-prd

仓库创建 2025年12月16日最近提交 8 天前SkillHot 收录 1 天前
▸ 精选理由

省去访谈,直接把现有上下文合成为可落地的产品文档

这个 Skill 做什么

从对话与代码库合成一份完整的 PRD 文件并写入项目

把当前对话和项目代码库合成一份完整的 PRD 并写进项目目录,省去再问一堆问题的环节。适合你已经讨论过需求、想把结论快速落到文件里并和代码库对齐的场景;它会读取仓库上下文、使用既有词汇和 ADRs 来写文档。特别的是直接生成项目内的 PRD 文件,强调合成而不是再做访谈。

▸ 展开 SKILL.md 英文原文

Turn the current conversation into a PRD file in the project folder — no interview, just synthesis of what you've already discussed.

开发编程PRD生成文档合成项目规划通用
208
Stars
26
Forks
32
仓库内 Skill
+6
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/serejaris/personal-corp-skills/main/skills/to-prd/SKILL.md
或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/serejaris/personal-corp-skills/main/skills/to-prd/SKILL.md"
SKILL.MD 节选查看完整文件 ↗
This skill takes the current conversation context and codebase understanding and produces a PRD. Do NOT interview the user — just synthesize what you already know.

## Process

1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the PRD, and respect any ADRs in the area you're touching.

2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.

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