Handbook

Sprint Structure

Epics should be product intersections, not product silos.

Updated

Planning hierarchy

Sprint planning hierarchy

How delivery intent decomposes from phase scope to governed sparks and reviewable evidence.

  1. PhaseTop-level delivery horizon that frames milestone goals.
  2. MilestoneA bounded checkpoint within the phase.
  3. Product-intersection EpicScoped work where multiple products meet, not one silo.
  4. User-visible StoryOutcome a user or operator can observe when done.
  5. SparkThe governed unit of agent-ready work with contracts and approval.
  6. Workcell PromptThe bounded prompt or workcell that executes the spark.
  7. Evidence PacketThe artifact bundle proving the spark is done.

Rule

Epics should be product intersections, not product silos.

Good:

EPIC-LENSES-LCDL-TRACE
EPIC-LENSES-FLEET-JOBS
EPIC-HERMES-BLUEPRINT-VERSONAS

Avoid:

EPIC-IMPROVE-LENSES
EPIC-IMPROVE-FLEET

Definition of ready

A Spark is ready only when it has:

  1. product owner,
  2. consuming product,
  3. contract touched,
  4. input schema,
  5. output schema,
  6. human approval boundary,
  7. evidence expectation,
  8. out-of-scope list,
  9. assigned prompt/workcell.

Definition of done

A Spark is done only when it returns evidence:

  • code or doc change exists,
  • tests or checks were run or explicitly waived,
  • schema/sample updated if applicable,
  • product boundary preserved,
  • consuming product can use the result,
  • evidence packet or sprint evidence note exists.