返回提示词目录第 1391 页

整理技术预研结论与决策报告

将预研问题与发现整理为简短报告,说明证据、未验证事项、结论可信度和后续行动。

完整提示词

<context>
A spike exists to buy knowledge, so its report is the product, not the code. Spike reports go wrong in predictable ways: they narrate the week instead of answering the question, they present a hacky prototype as if it were production-ready, they hide that the time box ran out before the hard part, or they quietly change the question to one that has a nicer answer. Readers (a tech lead, a planning meeting) need the answer, how sure you are, what would change it, and what the next step costs. Prototype code from a spike is usually meant to be thrown away, and the report should say so.
</context>

<task>
Write the spike report.

<question>
{{question}}
</question>

<findings>
{{findings}}
</findings>

1. Restate the original question and time box. If the findings answer a different or narrower question, say so explicitly instead of rewording the question.
2. Give the answer in one or two sentences: yes, no, or "yes, if ...", with the conditions.
3. Summarise the evidence: what was tried, what it showed, with any numbers from the notes. Keep it to what supports or weakens the answer.
4. List what was not tried or not tested because of the time box, and how each gap could change the answer.
5. Recommend the next step (build, run a second narrower spike, drop the idea, or decide between named options) with a rough size only if the notes support one.
6. Say what happens to the spike code: throw away, keep as reference, or the parts worth salvaging, and why.
</task>

<constraints>
- Do not invent results, numbers or tool behaviour that the notes do not contain.
- Do not upgrade "it worked once on my machine" into "it works"; state the conditions under which it was seen.
- Keep the report readable in three minutes: about 300 to 500 words.
{{> output/uncertainty}}
</constraints>

<output_format>
## Spike report
Question and time box, Answer, Evidence, Not covered, Recommendation, What to do with the spike code.

## Confidence
High, medium or low, with the one or two facts that most limit it.

## Gaps
Questions the notes leave open that a reviewer will ask, or "None".
</output_format>

可替换内容

  • {{question}}
  • {{findings}}
  • {{> output/uncertainty}}

分类与标签

办公效率、技术预研、决策报告、证据整理、评审材料

前往 AI 图片创作