Vision: make Ourocode the terminal-native front door for trusted Ouroboros plugins

[Q00]

Vision

Ourocode should become the terminal-native front door for trusted Ouroboros UserLevel plugins.

Users should be able to stay inside the Ourocode conversation loop, describe what they want, and let Ourocode resolve the right installed plugin, execute it through Ouroboros trust boundaries, surface the result, and continue into the generated workflow artifact when policy allows.

This builds on #2, which captures the concrete first feature request for dispatching installed UserLevel plugins such as superpowers from inside Ourocode.

Product Principle

Ourocode should not be another shell wrapper around ouroboros commands.

The product boundary should be:

1. Understand the user intent from direct commands or natural language.
2. Resolve installed, trusted Ouroboros plugin capabilities.
3. Dispatch through the existing Ouroboros plugin firewall and trust model.
4. Render plugin execution as a first-class Ourocode child session/pane.
5. Detect generated handoff artifacts such as seed.md.
6. Offer or perform the next workflow step according to explicit continuation policy.

The user should not need to manually switch tools, inspect internal run-storage directories, copy generated seed references, and return to ooo run by hand.

Target UX

Direct command

ooo superpowers test-driven-development --goal "Add retry behavior"

Expected behavior:

• Ourocode resolves superpowers as an installed UserLevel plugin.
• The command is dispatched through Ouroboros plugin trust/firewall semantics.
• Plugin output appears in the TUI as a child session or structured status pane.
• If a handoff artifact is generated, Ourocode detects it and shows the next step.

Natural language

Use the Superpowers TDD workflow to add retry behavior, then run the generated handoff.

Expected behavior:

• Ourocode resolves plugin intent only when plugin and command names are clear enough.
• Ambiguous requests trigger clarification rather than unsafe guessing.
• If the prompt explicitly asks to continue, Ourocode can invoke the generated ooo run seed_path=... path after artifact detection.

Non-Negotiable Constraints

• Do not bypass the Ouroboros plugin firewall.
• Do not execute arbitrary shell strings assembled from natural language.
• Do not silently install, trust, or grant plugin scopes.
• Destructive plugin actions remain blocked unless explicitly declared and trusted.
• Missing trust must surface actionable guidance, ideally the exact trust command from Ouroboros.

Proposed Product Milestones

Milestone 1: Direct trusted plugin dispatch

Support direct command-shaped prompts:

ooo <plugin> <command> [args]

Scope:

• resolve installed plugin and command metadata,
• construct a safe dispatch payload,
• call a stable Ouroboros plugin dispatch boundary,
• render output in Ourocode,
• surface trust-blocked states clearly.

Milestone 2: Artifact and handoff detection

Detect plugin-generated artifacts such as Seed-compatible handoffs and workflow reports exposed through the stable plugin artifact contract.

Scope:

• display generated artifact paths,
• identify Seed-compatible handoff files,
• show the next command, e.g. ooo run seed_path=...,
• preserve provenance and evidence paths for review.

Milestone 3: Conservative continuation policy

Allow continuation into ooo run only when policy allows.

Scope:

• read-only commands stop after output,
• handoff-generating commands suggest next steps by default,
• auto-run only when the user explicitly requested continuation,
• blocked/destructive actions require explicit trust and declaration.

Milestone 4: Natural-language plugin routing

Route natural-language prompts to plugin commands when confidence is high.

Scope:

• match installed plugin names and aliases,
• match command names and descriptions,
• ask clarification when multiple plugins/commands match,
• fall back to normal Ourocode routing when plugin intent is weak.

Success Criteria

• A user can run ooo superpowers list inside Ourocode without leaving the TUI.
• A user can run ooo superpowers test-driven-development --goal "..." and see generated plugin run artifacts.
• When seed.md is generated, Ourocode detects it and presents the next ooo run seed_path=... step.
• A natural-language request mentioning a known installed plugin and command can route to the same safe dispatch path.
• Trust-blocked or missing-plugin cases are helpful and non-destructive.
• Tests cover routing, dispatch payload construction, trust-blocked output, artifact detection, and continuation policy.

Relationship To #2

#2 is the concrete implementation request for installed UserLevel plugin dispatch.

This issue is the broader product vision and phased roadmap. It should remain open until the plugin-dispatch experience feels like a native Ourocode workflow rather than a documented workaround.