Files

T

KeyInfo Bot 9d6c8cded3 Separate Chinese display from plugin selector

Keep the installable plugin selector ASCII while restoring the Chinese user-facing display name for the patent drafting skill.\n\nConstraint: Codex marketplace entry name is the install selector and must remain ASCII kebab-case.\nRejected: Put Chinese in marketplace.json name | Codex list/add skips or fails to resolve that selector.\nConfidence: high\nScope-risk: narrow\nDirective: Use interface.displayName for Chinese aliases; never put localized text in plugin ids, directories, manifest name, or marketplace entry name.\nTested: python scripts/validate_marketplace.py; python /Users/eapil/.codex/skills/.system/plugin-creator/scripts/validate_plugin.py plugins/codex/plugins/patent-application-drafting-skill; temporary CODEX_HOME marketplace list and plugin add smoke test\nNot-tested: Interactive in-chat skill invocation was not rerun for this display-only change

2026-06-12 14:54:38 +08:00

1.6 KiB

Raw Blame History

Prometheus Strict

$prometheus-strict is a clean-room OMX planning skill for rigorous interview-driven planning before execution.

It is inspired by the high-level OMO Prometheus concept only. It does not copy OMO source text, prompts, runtime code, or workflow implementation.

Credit: Inspired by OMO Prometheus (code-yeongyu/oh-my-openagent), reimplemented from concept under MIT.

Roles

Metis clarifies requirements, constraints, non-goals, and acceptance criteria.
Momus challenges assumptions, scope, handoff risks, and missing verification.
Oracle synthesizes the approved plan and recommends the OMX-native handoff.

OMX Handoff

Prometheus Strict is planning-only by default. It should hand off to:

$ultragoal for durable goal execution.
$team only when the Oracle plan identifies independent parallel lanes.

Non-Goals

No hook implementation.
No Sisyphus or start-work port.
No direct implementation unless a downstream execution workflow is explicitly invoked.
No verbatim source copying from the inspiration project.

Expected Output

The skill returns a Prometheus Strict Plan with clarified requirements, resolved critique, an Oracle execution plan, a verification matrix, an optional durable artifact path under .omx/plans/prometheus-strict/, and clean-room credit.

Durable Plan Artifacts

When the plan should survive handoff or review, write the final Oracle synthesis to .omx/plans/prometheus-strict/<slug>.md and include that path in the plan before invoking $ultragoal or $team. Inline-only plans may set the artifact path to N/A - inline plan only.

1.6 KiB Raw Blame History