Spike Summary

Spike 总结

A spike summary documents the results of a time-boxed exploration . a focused investigation to reduce uncertainty before committing to implementation. Spikes answer specific questions like "Can we integrate with this API?" or "Is this technology viable for our use case?" The summary captures findings so the team can make informed decisions without the spike participants needing to repeat explanations.

Spike总结用于记录限时探索的结果——这是一种在投入实施前减少不确定性的针对性调查。Spike旨在解答特定问题，例如“我们能否集成该API？”或“这项技术是否适用于我们的使用场景？”总结会记录调查结果，以便团队能够做出明智决策，而无需Spike参与者反复解释相关内容。

When to Use

使用场景

After completing a time-boxed technical exploration
When evaluating technology choices or vendor options
After proof-of-concept work that needs to inform team decisions
When investigating feasibility of a proposed solution
Before committing engineering resources to a new approach

完成限时技术探索后
评估技术选型或供应商选项时
完成需要为团队决策提供依据的概念验证工作后
调查拟议解决方案的可行性时
为新方案投入工程资源前

Instructions

操作步骤

When asked to document a spike, follow these steps:

State the Question Clearly Articulate the specific question the spike was designed to answer. Good spike questions are focused and answerable with the time-box available. If the question evolved during the spike, document both the original and final versions.
Define the Time-Box Document the time allocated (e.g., 3 days) and actual time spent. If the spike exceeded its time-box, explain why and note any remaining work.
Describe the Approach Explain what was tried, in what order, and why. This helps future readers understand the methodology and whether alternative approaches were considered.
Present Findings with Evidence Document what was learned, supported by concrete evidence . code samples, performance benchmarks, screenshots, or API responses. Distinguish between verified findings and hypotheses that need more testing.
Make a Clear Recommendation Answer the original question directly: proceed, do not proceed, or proceed with conditions. Avoid hedging . the team needs actionable guidance.
Document Artifacts Link to any code, prototypes, diagrams, or documentation created during the spike. These artifacts often have ongoing value beyond the summary.
Capture Open Questions Note what the spike didn't answer and what additional investigation might be needed.

当需要记录Spike时，请遵循以下步骤：

明确提出问题 清晰阐述Spike旨在解答的具体问题。优质的Spike问题应聚焦明确，且在限时范围内可得到解答。如果在Spike执行过程中问题发生了变化，请同时记录原始问题和最终版本。
定义时限 记录分配的时间（例如3天）和实际花费的时间。如果Spike超出了时限，请说明原因并记录剩余工作内容。
描述实施方法 说明尝试了哪些内容、顺序如何以及原因。这有助于后续阅读者理解研究方法，以及是否考虑过其他替代方案。
结合证据呈现结果 记录所学内容，并辅以具体证据，例如代码示例、性能基准测试结果、截图或API响应。区分已验证的结果和需要进一步测试的假设。
给出明确建议 直接回答原始问题：推进、不推进，或有条件地推进。避免含糊其辞——团队需要可执行的指导意见。
记录相关工件 链接到Spike过程中创建的所有代码、原型、图表或文档。这些工件通常具有超出总结本身的长期价值。
记录未解决的问题 记录Spike未解答的问题以及可能需要进一步调查的内容。

Output Format

输出格式

Use the template in

references/TEMPLATE.md

to structure the output.

使用

references/TEMPLATE.md

中的模板来构建输出内容。

Quality Checklist

质量检查清单

Before finalizing, verify:

Original question is clearly stated
Time-box is documented (allocated vs. actual)
Findings are supported by evidence, not just opinions
Recommendation directly answers the question
Artifacts (code, diagrams) are linked or attached
Open questions identify remaining unknowns

定稿前，请确认：

已明确说明原始问题
已记录时限（分配时长vs实际时长）
结果有证据支持，而非仅为观点
建议直接回应了原始问题
已链接或附加相关工件（代码、图表等）
已记录未解决的问题，明确剩余未知项

Examples

示例

See

references/EXAMPLE.md

for a completed example.

请查看

references/EXAMPLE.md

中的完整示例。

develop-spike-summary

Original

Translation