Plugin route / Workflows

Four workflows. Loaded only when the task fits.

Gloamere Workflows adds four stable Skill identities with explicit trigger and exclusion boundaries. The bundle is installed once; Codex still decides which matching Skill to load.

Install Gloamere Workflows Browse source

task

UI systemvisual reviewknowledgedecision

Stable Skill surface

Each route earns its turn.

Installation does not preload all four workflows. Codex uses their descriptions and the user’s request to discover the relevant route.

gloamere-ui-system

UI System

Stable Skill identity · Beta vendor core

Use when: New UI, systematic redesign, design tokens, responsive behavior, or implementation constraints.
Produces: A coherent direction, token system, layout and state rules, accessibility boundaries, and stack-aware implementation guidance.
Boundary: Not for backend-only work, isolated functional bugs, copy editing, user research, or conversion experiments.

gloamere-visual-review

Visual Review

Stable Skill identity · Gloamere-authored

Use when: An existing interface, screenshot, design draft, component, or visual artifact needs an evidence-led review.
Produces: Visible observations, their user impact, up to three prioritized changes, and a concrete validation method.
Boundary: Not for creating a system from zero, text-only polish, or design advice without an inspectable artifact.

gloamere-knowledge-capture

Knowledge Capture

Stable Skill identity · Gloamere-authored

Use when: A conversation, research set, operating lesson, or project decision should become maintainable Markdown knowledge.
Produces: De-duplicated, linked records that preserve sources, status, dates, ownership, and open questions.
Boundary: Not for transient chat summaries, generic prose editing, or a one-off answer with no target knowledge base.

gloamere-product-decision

Product Decision

Stable Skill identity · Gloamere-authored

Use when: Existing research, data, and constraints need to converge into a scoped product choice.
Produces: A recommendation, evidence ledger, alternatives, tradeoffs, success measures, risks, open questions, and the next validation.
Boundary: Not for pretending research occurred, growth execution, internal operations, or implementation planning after the choice is made.

Provenance is part of the product

Original workflow contracts. One isolated vendor core.

original

Three Gloamere-authored Skills

Visual Review, Knowledge Capture, and Product Decision were rewritten around Gloamere’s own route boundaries, output contracts, and failure cases.

isolated

UI System vendor core

The GitHub beta candidate contains a pinned MIT UI data and helper core. Its exact file boundary, upstream commit, adjustment, and complete license notice are preserved.

GA gate

Original replacement required

Official-directory GA remains gated on replacing that vendor core with Gloamere-owned taxonomy, data, scripts, and rules, then rerunning identity, routing, and quality evaluations.

Read the full provenance record

LAB ≠ RELEASE

Experiments stay outside the plugin.

Repository labs may explore future workflows, but they are not bundled, supported, or presented as release Skills. Finance, growth, and general business-operations Skills are also outside the 4.0 beta candidate.

Pinned installation

Install only after the immutable beta tag is published.

These commands become valid only after the release gate passes and the exact tag is published. Nothing is fetched from a moving branch.

Codex CLIv4.0.0-beta.1

codex plugin marketplace add gloamere/codex-plugins --ref v4.0.0-beta.1codex plugin add gloamere-workflows@gloamerecodex plugin list --json

Default installer: installs Gloamere Eval.

Legacy safety: detects old 3.x selectors but never removes, disables, or modifies them.

PowerShell, macOS, and Linux installer commands