![Research Summary: [Project Name]](http://pic.xiahunao.cn/yaotu/Research Summary: [Project Name])
Research Summary: [Project Name]【免费下载链接】get-shit-doneA light-weight and powerful meta-prompting, context engineering and spec-driven development system for Claude Code by TÂCHES.项目地址: https://gitcode.com/GitHub_Trending/getshi/get-shit-doneDomain:[type of product]Researched:[date]Overall confidence:[HIGH/MEDIUM/LOW]Executive Summary[3-4 paragraphs synthesizing all findings]Key FindingsStack:[one-liner from STACK.md]Architecture:[one-liner from ARCHITECTURE.md]Critical pitfall:[most important from PITFALLS.md]Implications for RoadmapBased on research, suggested phase structure:[Phase name]- [rationale]Addresses: [features from FEATURES.md]Avoids: [pitfall from PITFALLS.md][Phase name]- [rationale] ...Phase ordering rationale:[Why this order based on dependencies]Research flags for phases:Phase [X]: Likely needs deeper research (reason)Phase [Y]: Standard patterns, unlikely to need researchConfidence AssessmentAreaConfidenceNotesStack[level][reason]Features[level][reason]Architecture[level][reason]Pitfalls[level][reason]Gaps to Address[Areas where research was inconclusive][Topics needing phase-specific research later]它由 gsd-research-synthesizer 负责写入见 [new-project 工作流](https://link.gitcode.com/i/8270b2ddad489139a2d895d12041c8b6) 中 subagent_typegsd-research-synthesizer 的调用是整个研究阶段对 roadmap 的唯一入口文档。 ### 8.2 STACK.md —— 总是产出带版本与理由的技术决策 markdown # Technology Stack **Project:** [name] **Researched:** [date] ## Recommended Stack ### Core Framework | Technology | Version | Purpose | Why | |------------|---------|---------|-----| | [tech] | [ver] | [what] | [rationale] | ### Database | Technology | Version | Purpose | Why | ### Infrastructure | Technology | Version | Purpose | Why | ### Supporting Libraries | Library | Version | Purpose | When to Use | ## Alternatives Considered | Category | Recommended | Alternative | Why Not | |----------|-------------|-------------|---------| ## Installation \\\bash # Core npm install [packages] # Dev dependencies npm install -D [packages] \\\ ## Sources - [Context7/official sources]对应栈维度子 Agent 的 prompt 中downstream_consumer要求其具体到库与版本、给出每个选择的理由、明确哪些不要用及为何不用。8.3 FEATURES.md —— 总是产出特性景观与 MVP 建议# Feature Landscape **Domain:** [type of product] **Researched:** [date] ## Table Stakes Features users expect. Missing product feels incomplete. | Feature | Why Expected | Complexity | Notes | |---------|--------------|------------|-------| ## Differentiators Features that set product apart. Not expected, but valued. | Feature | Value Proposition | Complexity | Notes | ## Anti-Features Features to explicitly NOT build. | Anti-Feature | Why Avoid | What to Do Instead | ## Feature Dependencies Feature A → Feature B (B requires A) ## MVP Recommendation Prioritize: 1. [Table stakes feature] 2. [Table stakes feature] 3. [One differentiator] Defer: [Feature]: [reason] ## Sources - [Competitor analysis, market research sources]Table Stakes / Differentiators / Anti-Features三分法是该文件的核心贡献它让 roadmap 知道哪些是没有用户会走的底线、哪些是值得在某个阶段做的差异点以及哪些是刻意不做避免范围蔓延。8.4 ARCHITECTURE.md —— 发现模式时产出# Architecture Patterns **Domain:** [type of product] **Researched:** [date] ## Recommended Architecture [Diagram or description] ### Component Boundaries | Component | Responsibility | Communicates With | |-----------|---------------|-------------------| ### Data Flow [How data flows through system] ## Patterns to Follow ### Pattern 1: [Name] **What:** [description] **When:** [conditions] **Example:** \\\typescript [code] \\\ ## Anti-Patterns to Avoid ### Anti-Pattern 1: [Name] **What:** [description] **Why bad:** [consequences] **Instead:** [what to do] ## Scalability Considerations | Concern | At 100 users | At 10K users | At 1M users | |---------|--------------|--------------|-------------| ## Sources - [Architecture references]架构维度的子 Agent prompt 明确要求写清楚组件边界谁跟谁通信、数据流方向、以及组件之间的构建顺序依赖——后者直接映射为 roadmap 的阶段次序。8.5 PITFALLS.md —— 总是产出分级陷阱目录# Domain Pitfalls **Domain:** [type of product] **Researched:** [date] ## Critical Pitfalls Mistakes that cause rewrites or major issues. ### Pitfall 1: [Name] **What goes wrong:** [description] **Why it happens:** [root cause] **Consequences:** [what breaks] **Prevention:** [how to avoid] **Detection:** [warning signs] ## Moderate Pitfalls ### Pitfall 1: [Name] **What goes wrong:** [description] **Prevention:** [how to avoid] ## Minor Pitfalls ### Pitfall 1: [Name] ## Phase-Specific Warnings | Phase Topic | Likely Pitfall | Mitigation | |-------------|---------------|------------| ## Sources - [Post-mortems, issue discussions, community wisdom]陷阱维度要求按严重度分级会导致重写的 / 中等 / 轻微并尽量映射到哪个阶段应处理它从而让 roadmap 的每个阶段自带风险预警。8.6 COMPARISON.md / FEASIBILITY.md —— 模式化条件产出Comparison 模式下的COMPARISON.md结构为上下文与一句式推荐 → Quick Comparison 矩阵各方案逐标准评级→ 每个方案的 Strengths/Weaknesses/Best for → 1–2 段推荐结论 → 明确给出 Choose [A] when:conditions /Choose [B] when:conditions并以带置信度的来源列表收尾。Feasibility 模式下的FEASIBILITY.md结构为VerdictYES/NO/MAYBE 条件与 Confidence → 2–3 段摘要 → Requirements 状态表available/partial/missing→ Blockers 表high/medium/low mitigation→ Recommendation → Sources。九、执行流程Execution Flowexecution_flow定义了六步可复用的执行序列Step 1: Receive Research Scope—— orchestrator 提供项目名/描述、研究模式、项目上下文与具体问题先解析并确认再行动。Step 2: Identify Research Domains—— 从四个维度出发Technology框架、标准栈、新兴替代、Featurestable stakes / differentiators / anti-features、Architecture系统结构、组件边界、模式、Pitfalls常见错误、重写原因、隐藏复杂度。Step 3: Execute Research—— 对每个领域按 Context7 → Official Docs → WebSearch → Verify 推进并用置信度标注。Step 4: Quality Check—— 执行上文 Pre-Submission Checklist。Step 5: Write Output Files——始终用 Write 工具创建文件禁止用Bash(cat EOF)或 heredoc这是一个可测试的执行约束在.planning/research/下按SUMMARY.md 恒写、STACK.md 恒写、FEATURES.md 恒写、ARCHITECTURE.md 视模式、PITFALLS.md 恒写、COMPARISON/FEASIBILITY 视模式的规则落盘。Step 6: Return Structured Result——不提交DO NOT commit因为它是与其他研究员并行派生的由 orchestrator 在全部完成后统一提交。十、结构化返回正常完成与受阻两条通道Agent 结束时必须向 orchestrator 返回结构化结果文档定义了两种形态。正常完成Research Complete## RESEARCH COMPLETE **Project:** {project_name} **Mode:** {ecosystem/feasibility/comparison} **Confidence:** [HIGH/MEDIUM/LOW] ### Key Findings [3-5 bullet points of most important discoveries] ### Files Created | File | Purpose | |------|---------| | .planning/research/SUMMARY.md | Executive summary with roadmap implications | | .planning/research/STACK.md | Technology recommendations | | .planning/research/FEATURES.md | Feature landscape | | .planning/research/ARCHITECTURE.md | Architecture patterns | | .planning/research/PITFALLS.md | Domain pitfalls | ### Confidence Assessment | Area | Level | Reason | ### Roadmap Implications [Key recommendations for phase structure] ### Open Questions [Gaps that couldnt be resolved, need phase-specific research later]研究受阻Research Blocked## RESEARCH BLOCKED **Project:** {project_name} **Blocked by:** [whats preventing progress] ### Attempted [What was tried] ### Options 1. [Option to resolve] 2. [Alternative approach] ### Awaiting [Whats needed to continue]【免费下载链接】get-shit-doneA light-weight and powerful meta-prompting, context engineering and spec-driven development system for Claude Code by TÂCHES.项目地址: https://gitcode.com/GitHub_Trending/getshi/get-shit-done创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考
Research Summary: [Project Name]
Research Summary: [Project Name]【免费下载链接】get-shit-doneA light-weight and powerful meta-prompting, context engineering and spec-driven development system for Claude Code by TÂCHES.项目地址: https://gitcode.com/GitHub_Trending/getshi/get-shit-doneDomain:[type of product]Researched:[date]Overall confidence:[HIGH/MEDIUM/LOW]Executive Summary[3-4 paragraphs synthesizing all findings]Key FindingsStack:[one-liner from STACK.md]Architecture:[one-liner from ARCHITECTURE.md]Critical pitfall:[most important from PITFALLS.md]Implications for RoadmapBased on research, suggested phase structure:[Phase name]- [rationale]Addresses: [features from FEATURES.md]Avoids: [pitfall from PITFALLS.md][Phase name]- [rationale] ...Phase ordering rationale:[Why this order based on dependencies]Research flags for phases:Phase [X]: Likely needs deeper research (reason)Phase [Y]: Standard patterns, unlikely to need researchConfidence AssessmentAreaConfidenceNotesStack[level][reason]Features[level][reason]Architecture[level][reason]Pitfalls[level][reason]Gaps to Address[Areas where research was inconclusive][Topics needing phase-specific research later]它由 gsd-research-synthesizer 负责写入见 [new-project 工作流](https://link.gitcode.com/i/8270b2ddad489139a2d895d12041c8b6) 中 subagent_typegsd-research-synthesizer 的调用是整个研究阶段对 roadmap 的唯一入口文档。 ### 8.2 STACK.md —— 总是产出带版本与理由的技术决策 markdown # Technology Stack **Project:** [name] **Researched:** [date] ## Recommended Stack ### Core Framework | Technology | Version | Purpose | Why | |------------|---------|---------|-----| | [tech] | [ver] | [what] | [rationale] | ### Database | Technology | Version | Purpose | Why | ### Infrastructure | Technology | Version | Purpose | Why | ### Supporting Libraries | Library | Version | Purpose | When to Use | ## Alternatives Considered | Category | Recommended | Alternative | Why Not | |----------|-------------|-------------|---------| ## Installation \\\bash # Core npm install [packages] # Dev dependencies npm install -D [packages] \\\ ## Sources - [Context7/official sources]对应栈维度子 Agent 的 prompt 中downstream_consumer要求其具体到库与版本、给出每个选择的理由、明确哪些不要用及为何不用。8.3 FEATURES.md —— 总是产出特性景观与 MVP 建议# Feature Landscape **Domain:** [type of product] **Researched:** [date] ## Table Stakes Features users expect. Missing product feels incomplete. | Feature | Why Expected | Complexity | Notes | |---------|--------------|------------|-------| ## Differentiators Features that set product apart. Not expected, but valued. | Feature | Value Proposition | Complexity | Notes | ## Anti-Features Features to explicitly NOT build. | Anti-Feature | Why Avoid | What to Do Instead | ## Feature Dependencies Feature A → Feature B (B requires A) ## MVP Recommendation Prioritize: 1. [Table stakes feature] 2. [Table stakes feature] 3. [One differentiator] Defer: [Feature]: [reason] ## Sources - [Competitor analysis, market research sources]Table Stakes / Differentiators / Anti-Features三分法是该文件的核心贡献它让 roadmap 知道哪些是没有用户会走的底线、哪些是值得在某个阶段做的差异点以及哪些是刻意不做避免范围蔓延。8.4 ARCHITECTURE.md —— 发现模式时产出# Architecture Patterns **Domain:** [type of product] **Researched:** [date] ## Recommended Architecture [Diagram or description] ### Component Boundaries | Component | Responsibility | Communicates With | |-----------|---------------|-------------------| ### Data Flow [How data flows through system] ## Patterns to Follow ### Pattern 1: [Name] **What:** [description] **When:** [conditions] **Example:** \\\typescript [code] \\\ ## Anti-Patterns to Avoid ### Anti-Pattern 1: [Name] **What:** [description] **Why bad:** [consequences] **Instead:** [what to do] ## Scalability Considerations | Concern | At 100 users | At 10K users | At 1M users | |---------|--------------|--------------|-------------| ## Sources - [Architecture references]架构维度的子 Agent prompt 明确要求写清楚组件边界谁跟谁通信、数据流方向、以及组件之间的构建顺序依赖——后者直接映射为 roadmap 的阶段次序。8.5 PITFALLS.md —— 总是产出分级陷阱目录# Domain Pitfalls **Domain:** [type of product] **Researched:** [date] ## Critical Pitfalls Mistakes that cause rewrites or major issues. ### Pitfall 1: [Name] **What goes wrong:** [description] **Why it happens:** [root cause] **Consequences:** [what breaks] **Prevention:** [how to avoid] **Detection:** [warning signs] ## Moderate Pitfalls ### Pitfall 1: [Name] **What goes wrong:** [description] **Prevention:** [how to avoid] ## Minor Pitfalls ### Pitfall 1: [Name] ## Phase-Specific Warnings | Phase Topic | Likely Pitfall | Mitigation | |-------------|---------------|------------| ## Sources - [Post-mortems, issue discussions, community wisdom]陷阱维度要求按严重度分级会导致重写的 / 中等 / 轻微并尽量映射到哪个阶段应处理它从而让 roadmap 的每个阶段自带风险预警。8.6 COMPARISON.md / FEASIBILITY.md —— 模式化条件产出Comparison 模式下的COMPARISON.md结构为上下文与一句式推荐 → Quick Comparison 矩阵各方案逐标准评级→ 每个方案的 Strengths/Weaknesses/Best for → 1–2 段推荐结论 → 明确给出 Choose [A] when:conditions /Choose [B] when:conditions并以带置信度的来源列表收尾。Feasibility 模式下的FEASIBILITY.md结构为VerdictYES/NO/MAYBE 条件与 Confidence → 2–3 段摘要 → Requirements 状态表available/partial/missing→ Blockers 表high/medium/low mitigation→ Recommendation → Sources。九、执行流程Execution Flowexecution_flow定义了六步可复用的执行序列Step 1: Receive Research Scope—— orchestrator 提供项目名/描述、研究模式、项目上下文与具体问题先解析并确认再行动。Step 2: Identify Research Domains—— 从四个维度出发Technology框架、标准栈、新兴替代、Featurestable stakes / differentiators / anti-features、Architecture系统结构、组件边界、模式、Pitfalls常见错误、重写原因、隐藏复杂度。Step 3: Execute Research—— 对每个领域按 Context7 → Official Docs → WebSearch → Verify 推进并用置信度标注。Step 4: Quality Check—— 执行上文 Pre-Submission Checklist。Step 5: Write Output Files——始终用 Write 工具创建文件禁止用Bash(cat EOF)或 heredoc这是一个可测试的执行约束在.planning/research/下按SUMMARY.md 恒写、STACK.md 恒写、FEATURES.md 恒写、ARCHITECTURE.md 视模式、PITFALLS.md 恒写、COMPARISON/FEASIBILITY 视模式的规则落盘。Step 6: Return Structured Result——不提交DO NOT commit因为它是与其他研究员并行派生的由 orchestrator 在全部完成后统一提交。十、结构化返回正常完成与受阻两条通道Agent 结束时必须向 orchestrator 返回结构化结果文档定义了两种形态。正常完成Research Complete## RESEARCH COMPLETE **Project:** {project_name} **Mode:** {ecosystem/feasibility/comparison} **Confidence:** [HIGH/MEDIUM/LOW] ### Key Findings [3-5 bullet points of most important discoveries] ### Files Created | File | Purpose | |------|---------| | .planning/research/SUMMARY.md | Executive summary with roadmap implications | | .planning/research/STACK.md | Technology recommendations | | .planning/research/FEATURES.md | Feature landscape | | .planning/research/ARCHITECTURE.md | Architecture patterns | | .planning/research/PITFALLS.md | Domain pitfalls | ### Confidence Assessment | Area | Level | Reason | ### Roadmap Implications [Key recommendations for phase structure] ### Open Questions [Gaps that couldnt be resolved, need phase-specific research later]研究受阻Research Blocked## RESEARCH BLOCKED **Project:** {project_name} **Blocked by:** [whats preventing progress] ### Attempted [What was tried] ### Options 1. [Option to resolve] 2. [Alternative approach] ### Awaiting [Whats needed to continue]【免费下载链接】get-shit-doneA light-weight and powerful meta-prompting, context engineering and spec-driven development system for Claude Code by TÂCHES.项目地址: https://gitcode.com/GitHub_Trending/getshi/get-shit-done创作声明：本文部分内容由AI辅助生成（AIGC），仅供参考
