Graph router, picks the appropriate graph for the task

cmoriarty commented

2026-09-18 20:05:43 -04:00

Owner

When using OpenSpec, I often skip the proposal change process if the change is a trivial UI fix for example. For that, you could implement the fix without the OpenSpec overhead, and instead still follow steps to follow good software engineering practices (branch, unit tests, UI tests, update CI, PR with summary of changes, etc).

For this, there is a new concept being introduced that is a tier above a graph, perhaps we call it methodology. At that level you can make some choices (wizard) or choose between options like "feature branching", "feature branching with OpenSpec", "git flow", "git flow with OpenSpec". From there each will have multiple graphs, for example the trivial UI fix would not use OpenSpec even if that was the methodology.

One solution is for there to be an initial (new) step in all (or most) graphs that follows the methodology, but still may choose to change the graph used to implement the change, as in the trivial UI fix example I used, which would skip OpenSpec even if that was the methodology, but still follows feature branching or git flow processes.

When using OpenSpec, I often skip the proposal change process if the change is a trivial UI fix for example. For that, you could implement the fix without the OpenSpec overhead, and instead still follow steps to follow good software engineering practices (branch, unit tests, UI tests, update CI, PR with summary of changes, etc). For this, there is a new concept being introduced that is a tier above a graph, perhaps we call it methodology. At that level you can make some choices (wizard) or choose between options like "feature branching", "feature branching with OpenSpec", "git flow", "git flow with OpenSpec". From there each will have multiple graphs, for example the trivial UI fix would not use OpenSpec even if that was the methodology. One solution is for there to be an initial (new) step in all (or most) graphs that follows the methodology, but still may choose to change the graph used to implement the change, as in the trivial UI fix example I used, which would skip OpenSpec even if that was the methodology, but still follows feature branching or git flow processes.

cmoriarty referenced this issue

2026-09-27 12:01:50 -04:00

New Run as a wizard: detect OpenSpec and git flow, narrow the pipelines, and name them properly #88

cmoriarty referenced this issue

2026-09-27 17:29:52 -04:00

New Run as a wizard: detect OpenSpec and git flow, narrow the pipelines, and name them properly #88

Rows
Columns

Graph router, picks the appropriate graph for the task #43