skills.rest
BetaS
BetaSCOMMUNITY
Explore all skills by this author →
GitHub

prometheus-strict

Coordinate Metis, Momus, and Oracle for interview-driven OMX planning.

Updated May 25, 2026
Search Tags:#workflow#planning#risk mitigation#structured questioning#omx
One-click install
npx skills add https://github.com/BetaS/swm-gis-workshop --skill prometheus-strict-betas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prometheus-strict
Source: https://github.com/BetaS/swm-gis-workshop/tree/main/.codex/skills/prometheus-strict
Command: npx skills add https://github.com/BetaS/swm-gis-workshop --skill prometheus-strict-betas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures a thorough, interview-driven planning process for OMX workflows, mitigating risks and clarifying requirements before execution.

Core Features & Use Cases

  • Interview-Driven Planning: Metis clarifies requirements, Momus challenges assumptions, and Oracle synthesizes a handoff-ready plan.
  • OMX Handoff: Hand off to $ultragoal or $team based on the Oracle's assessment of independent lanes.
  • Durable Plan Artifacts: Store final plans for review or handoff to downstream workflows.

Quick Start

Use the prometheus-strict skill to create a plan for your OMX workflow, considering requirements, constraints, and acceptance criteria.

Frequently Asked Questions about prometheus-strict

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How does interview-driven planning mitigate workflow risks before execution?▼

Interview-driven planning mitigates workflow risks by using structured questioning to clarify requirements, challenge assumptions, and synthesize a handoff-ready plan before execution begins.

What is the best way to plan complex OMX workflows requiring risk mitigation?▼

The best way to plan complex OMX workflows is using a rigorous planning skill that engages Metis to clarify requirements, Momus to challenge assumptions, and Oracle to synthesize plans.

Do I need OMX planning conventions to use structured questioning for workflow planning?▼

Yes, you need OMX planning conventions and structured questioning techniques to effectively use this interview-driven planning process and generate durable plan artifacts.

How do I store final plans for review or handoff to downstream workflows?▼

You store final plans as durable plan artifacts after the Oracle synthesizes the interview-driven planning process, making them available for review or downstream workflow handoff.

When should I hand off to $ultragoal or $team during OMX planning?▼

You hand off to $ultragoal or $team based on the Oracle's assessment of independent lanes after Metis clarifies requirements and Momus challenges assumptions in the planning process.

Related Skills

Explore More Software Engineering Skills→
ksciuskscius
2

requirements-gathering

Transforms vague requests into structured briefs with acceptance criteria and scope.

Community
Advanced
OrinksOrinks
24

ultrawork

Coordinate parallel independent tasks with evidence sharing and pass/fail criteria.

Community
Advanced
JaCha00JaCha00

prometheus-strict

Interview-driven planning for OMX workflows with clean-room boundaries.

Community
Advanced
DevelopersGlobalDevelopersGlobal
65

task-decomposition

Break down complex project features into smaller, independently executable tasks.

Official
Advanced