Forge-Spark — Forge Spark

Smallest delivery unit (~1–4h task) in core Forge — phase-prefixed discover:/specify:/…; maps to WBS Task.

Guide · Updated · Source

What it is

Executable work in Charge daily commitment under core Forge. Not exploration spike or Product Spark. Under the Epic execution profile, Forge Spark is not a Charge work item — L1–L2 agent scratch inside a Charged Epic only.

When people say this

When sizing day work, writing spark notes in forge-logs/, or linking commits to tasks — core Forge profile.

Where it lives

blueprints/sdlc/methodologies/forge/process-and-flows.md

How it fits the ecosystem

Core Forge: Spark → Charge (view, not Kanban SoT). Epic execution profile: Charge lists Epics instead; Story/Task/Spark are runs inside the Epic — do not mint …T{n} Charge rows. forge repo abbr is unrelated to Spark task noun.

Typical usage in plans and chat

Phase-prefixed spark ids in plans clarify which SDLC phase owns the task (core). Under the Epic execution profile, execute inside the Charged Epic via OpenSpec — do not add Forge Sparks to Charge.

Do not confuse with

forge Product-Spark

Disambiguation bridges

Term page — canonical catalog entry forge-spark.