Forge Platform

Handbook

Sprint Structure

Epics should be product intersections, not product silos.

Planning hierarchy

Phase
  -> Milestone
    -> Product-intersection Epic
      -> User-visible Story
        -> Spark
          -> Workcell Prompt
            -> Evidence Packet

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.