Opi Workflow Router
Route work to the skill that owns the next decision or artifact. This skill is
an index, not an orchestrator: open the selected skill before making any
load-bearing claim, and stop at human decision and irreversible boundaries.
Design direction
- Inward: pi is opi's design reference. Use
opi-realign to measure the
latest pi direction against the Rust implementation and selected opi scope.
- Outward: optional capabilities beyond or poorly served by pi are researched
for plugin/package placement before expanding core. Use
opi-research.
- Implementation:
.opi-impl-state.json and opi-implement are the only
delivery state machine. Do not introduce another ticket, plan, worktree, or
commit protocol inside it.
Routes
| Situation |
Open and use |
| Compare current opi with the latest pi design or implementation |
opi-realign |
| Investigate an external or non-pi capability |
opi-research |
| Resolve a large, multi-session decision space with fog |
Recommend explicit Matt wayfinder, after the tracker adapter check below |
| Sharpen bounded ambiguity in the current session |
Recommend explicit Matt grill-with-docs, with the opi glossary adapter below |
| Synthesize settled decisions when no reviewed spec exists |
Recommend explicit Matt to-spec, producing a non-normative tracker candidate |
| Admit a reviewed, registered source and construct its task graph |
opi-implement plan |
| Execute an admitted ledger task |
opi-implement |
| Diagnose a hard bug or performance regression |
Matt diagnosing-bugs, then return to the owning delivery route |
| Audit a completed phase |
opi-audit |
| Validate and optionally fix normalized findings |
opi-remediate |
| Gather release-candidate runtime evidence |
opi-eval |
| Synchronize product documentation |
opi-document |
| Publish a verified release |
opi-release |
| Reduce integration-test binary count |
opi-slim-tests |
Direct invocation of any routed skill is valid. Do not call a skill merely to
make the route look complete: skip to-spec when wayfinding already produced a
reviewed spec, and skip assurance or release work whose entry gate is not met.
Matt adapter contract
wayfinder, grill-with-docs, to-spec, and
setup-matt-pocock-skills are user-invoked Matt skills. Return the exact
recommended invocation and stop; do not claim to invoke or compose them from
this router.- Before recommending
wayfinder or to-spec, require
docs/agents/issue-tracker.md. If it is absent, recommend explicit Matt
setup-matt-pocock-skills and stop until the tracker is configured. Do not
invent tracker conventions inside an opi skill.
- When
wayfinder or grill-with-docs invokes Matt domain-modeling, bind its
glossary target to opi's existing docs/CONTEXT.md and its ADR target to
docs/adr/. Do not create a competing root CONTEXT.md.
- A wayfinder map, decision ticket, or
to-spec tracker issue is shaping
evidence, not an opi-implement source. Human review must materialize the
settled result into docs/opi-spec.md or a supplemental spec registered by
opi-implement; only then may opi-implement plan admit it.
Phase boundaries
- Research and realignment produce evidence, not product decisions.
- Human-led shaping may return to either evidence path repeatedly.
opi-implement plan is an adversarial admission check, not a shaping tool.opi-implement cannot silently amend a normative source when meaning is
missing or wrong; it returns to the owning shaping artifact.- Audit does not fix, eval does not fix, documentation does not release, and
release does not cross an irreversible boundary without explicit approval.
When a required routed skill is unavailable, stop with a setup error. Do not
silently substitute a similarly named workflow from another skill package.
1---2name: opi-workflow3description: Route opi work among inward pi realignment, outward capability research, human-led shaping, delivery, assurance, documentation, and release without creating a second state machine.4---56# Opi Workflow Router78Route work to the skill that owns the next decision or artifact. This skill is9an index, not an orchestrator: open the selected skill before making any10load-bearing claim, and stop at human decision and irreversible boundaries.1112## Design direction1314- **Inward:** pi is opi's design reference. Use `opi-realign` to measure the15 latest pi direction against the Rust implementation and selected opi scope.16- **Outward:** optional capabilities beyond or poorly served by pi are researched17 for plugin/package placement before expanding core. Use `opi-research`.18- **Implementation:** `.opi-impl-state.json` and `opi-implement` are the only19 delivery state machine. Do not introduce another ticket, plan, worktree, or20 commit protocol inside it.2122## Routes2324| Situation | Open and use |25|---|---|26| Compare current opi with the latest pi design or implementation | `opi-realign` |27| Investigate an external or non-pi capability | `opi-research` |28| Resolve a large, multi-session decision space with fog | Recommend explicit Matt `wayfinder`, after the tracker adapter check below |29| Sharpen bounded ambiguity in the current session | Recommend explicit Matt `grill-with-docs`, with the opi glossary adapter below |30| Synthesize settled decisions when no reviewed spec exists | Recommend explicit Matt `to-spec`, producing a non-normative tracker candidate |31| Admit a reviewed, registered source and construct its task graph | `opi-implement plan` |32| Execute an admitted ledger task | `opi-implement` |33| Diagnose a hard bug or performance regression | Matt `diagnosing-bugs`, then return to the owning delivery route |34| Audit a completed phase | `opi-audit` |35| Validate and optionally fix normalized findings | `opi-remediate` |36| Gather release-candidate runtime evidence | `opi-eval` |37| Synchronize product documentation | `opi-document` |38| Publish a verified release | `opi-release` |39| Reduce integration-test binary count | `opi-slim-tests` |4041Direct invocation of any routed skill is valid. Do not call a skill merely to42make the route look complete: skip `to-spec` when wayfinding already produced a43reviewed spec, and skip assurance or release work whose entry gate is not met.4445## Matt adapter contract4647- `wayfinder`, `grill-with-docs`, `to-spec`, and48 `setup-matt-pocock-skills` are user-invoked Matt skills. Return the exact49 recommended invocation and stop; do not claim to invoke or compose them from50 this router.51- Before recommending `wayfinder` or `to-spec`, require52 `docs/agents/issue-tracker.md`. If it is absent, recommend explicit Matt53 `setup-matt-pocock-skills` and stop until the tracker is configured. Do not54 invent tracker conventions inside an opi skill.55- When `wayfinder` or `grill-with-docs` invokes Matt `domain-modeling`, bind its56 glossary target to opi's existing `docs/CONTEXT.md` and its ADR target to57 `docs/adr/`. Do not create a competing root `CONTEXT.md`.58- A wayfinder map, decision ticket, or `to-spec` tracker issue is shaping59 evidence, not an `opi-implement` source. Human review must materialize the60 settled result into `docs/opi-spec.md` or a supplemental spec registered by61 `opi-implement`; only then may `opi-implement plan` admit it.6263## Phase boundaries6465- Research and realignment produce evidence, not product decisions.66- Human-led shaping may return to either evidence path repeatedly.67- `opi-implement plan` is an adversarial admission check, not a shaping tool.68- `opi-implement` cannot silently amend a normative source when meaning is69 missing or wrong; it returns to the owning shaping artifact.70- Audit does not fix, eval does not fix, documentation does not release, and71 release does not cross an irreversible boundary without explicit approval.7273When a required routed skill is unavailable, stop with a setup error. Do not74silently substitute a similarly named workflow from another skill package.
OdradekAI