canon-backlog

Decomposing bounded decisions into epics and slices for backlog governance requires Canon installed on PATH and a .canon/ working directory. The Skill automates this decomposition to produce structured planning outputs with traceability and alignment.

A governed backlog run automates decomposing upstream decisions into epics, slices, and priorities while maintaining traceability and closure findings across the lifecycle. You need it when your bounded backlog brief requires auditable delivery and alignment.

Yes, you need Canon installed and available on PATH, a .canon/ working directory, and a binding --system-context that exists. You also need at least one authored input and proper risk and zone values to initiate the backlog workflow.

To start a backlog run in Canon, tell your AI assistant to initiate a backlog run in backlog mode using the canonical backlog inputs and system context. This automates the creation of epics, slices, dependencies, and sequencing for your bounded decisions.

Maintaining traceability and closure findings across the backlog lifecycle is best achieved through a governed run that produces a durable packet lifecycle. Canon backlog management automates this auditable delivery by decomposing bounded upstream decisions into structured priorities.

Canon backlog runs require proper risk and zone values because they are part of the governed backlog workflow prerequisites. Without these values and at least one authored input, the Skill cannot apply the Canon system context binding to decompose your bounded decisions.