trd-write
仓库创建 2026年6月24日最近提交 23 天前SkillHot 收录 22 天前
▸ 精选理由
把产品需求落地为可执行的技术计划与里程碑。
这个 Skill 做什么
把 PRD 转为高层 TRD，分阶段规划技术实现路径。
把产品需求(PRD)翻成可执行的高级技术计划(TRD)，按阶段拆出里程碑、实现路径和重要技术决策。要把一个功能或史诗从“要做什么”变成“怎么做”时使用，或在更新现有 TRD 时用。特色是强调分阶段可交付、把假设显性化，帮助下游拆票和评估实现风险与成本。
▸ 展开 SKILL.md 英文原文
Create and update a Technical Requirements Document (TRD) — the epic-level technical plan for how a PRD gets built: an overview of why, then the implementation broken into stages. Use when the user wants to write a TRD, plan out an epic, spec a feature technically, turn a PRD into a technical plan, or update an existing TRD.
0
Stars
0
Forks
5
仓库内 Skill
+0
7 日增星
安装 / 使用
给你的 Agent 一句话（通用）
帮我安装这个 skill：https://raw.githubusercontent.com/juff17/docify/master/skills/trd-write/SKILL.md或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/juff17/docify/master/skills/trd-write/SKILL.md"SKILL.MD 节选查看完整文件 ↗
A TRD is the **high-level technical plan** for building a PRD (product requirements document). The PRD says *what* we're building and why; the TRD answers *how*. A TRD is a **plan**, and every stage and ticket downstream gets built from it. That makes assumptions expensive: a wrong guess about scope, a requirement, a constraint, or a decision propagates into everything that follows. So when something material is unknown, undecided, or ambiguous, **ask the user — don't assume.** Resolve these in conversation *before* drafting — they're decisions where the user's intent matters and you can't settle them by reading the codebase: - **the approach**, when there's a real fork — build vs. integr
via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有