plan-by-surface-repo-layer-signal

To categorize a backlog by surface, repo, layer, and signal, this Skill processes queued items across those four axes and generates a master plan with per-repo sub-plans. It handles inputs from inline backlogs, CORTEX tasks, and repo state signals.

Generating a master plan with sub-plans for backlog execution involves categorizing queued items by surface, repo, layer, and signal. This Skill produces a mermaid DAG alongside an embedded execution recipe for downstream orchestrator dispatch.

Yes, you can use inline backlogs and repo state signals for backlog planning. This Skill accepts inputs from CORTEX tasks, inline backlogs, and repo state signals, resolving portable paths and following specific scope boundaries to categorize items.

Yes, backlog planning by surface and repo requires authorization for merge-on-all-gates-PASS. This ensures that the generated master plan and execution recipes align with authorized project requirements before downstream orchestrator dispatch.

Categorizing backlog items by signal and layer generates an execution recipe by mapping queued tasks across four axes: surface, repo, layer, and signal. The output embeds this recipe directly into per-repo sub-plans for orchestrator dispatch.