---
type: Template
title: Spike Brief Template
description: The scaffold for a discovery-lane spike brief (D56) — question, timebox, spend cap, disposition. Copy into /planning/prd/ as <id>-spike.md and set it as the initiative's prd_path; the lighter spec artifact the discovery lane requires instead of a PRD.
tags: [template, discovery, spike, lanes]
timestamp: 2026-07-17
---

# Spike Brief Template

**Situating context:** Authored with [D56](/okf/products/pmos/adr/d56-initiative-lanes.md) as the
discovery lane's spec artifact, resolving the eval-first paradox the SDLC stress test named: a
prototype exists to *discover* its own done-criteria, so the lane contracts on a **question and a
timebox**, not on requirements. The [discovery skill](/skills/discovery.skill) instantiates
this template. Copy the block below into `/planning/prd/<id>-spike.md` and fill; the copy is an
operational instance, not OKF knowledge.

> Usage: replace every `<…>` placeholder. An empty question or a missing timebox means the brief is
> not ready. The disposition section stays open until the spike closes — closing it is mandatory.

---

```markdown
# Spike Brief: <initiative title>

## Identity
- initiative_id: <id>
- type: discovery
- product_slug: <product_slug>
- pm_slug: <pm_slug>
- parent_KR: <objective/KR reference OR health:<id> (D59)>   <!-- REQUIRED — anchoring holds in every lane. -->
- status: open | closed
- date: <YYYY-MM-DD>

## Question
<!-- The ONE question this spike answers. If you can write done-criteria instead, it is not a
     spike — take the feature lane. -->

## Why now
<!-- What decision or initiative is blocked on this answer. -->

## Timebox & spend cap
- timebox: <e.g. 2 days / 3 runs>       <!-- REQUIRED. The spike ends when the box ends, answered or not. -->
- spend_cap: <e.g. token/infra budget, if relevant>

## Method sketch
<!-- How you'll attack it — rough is fine; the path is not graded (D14). Throwaway code is
     expected and stays on the initiative branch. -->

## Out of scope
<!-- What this spike deliberately does NOT try to answer or build. -->

## Disposition (fill at close — mandatory)
- disposition: learned | promoted | discarded
- evidence: <what was learned, one paragraph — link artifacts/branch>
- follow-up: <for `promoted`: link the NEW feature-lane initiative + PRD; a spike never silently
  becomes the product. For `discarded`: one line on why.>
```

---

## Authoring checklist

- [ ] `parent_KR` present — discovery is anchored work, not free exploration.
- [ ] The question is singular and answerable inside the timebox.
- [ ] Timebox stated; the spike ends when it ends (inconclusive is a valid, recordable outcome).
- [ ] Disposition closed before the initiative leaves the board — `promoted` links a real
      feature-lane PRD; prototype code is deleted or explicitly quarantined, never shipped as-is.