prometheus-strict

Generates interview-driven execution plans through clarification, critique, and synthesis roles.

Updated Feb 1, 2024
One-click install
npx skills add https://github.com/ogiboy/portfolio-app --skill prometheus-strict-ogiboy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prometheus-strict
Source: https://github.com/ogiboy/portfolio-app/tree/main/.codex/skills/prometheus-strict
Command: npx skills add https://github.com/ogiboy/portfolio-app --skill prometheus-strict-ogiboy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ambiguous or high-stakes tasks often get executed with incomplete requirements, leading to wrong work. This Skill enforces a rigorous planning phase before execution: it interviews you to clarify requirements, challenges assumptions adversarially, and synthesizes a verified, handoff-ready plan. ## Core Features & Use Cases - Three-Role Planning Loop: Metis clarifies requirements and acceptance criteria, Momus challenges assumptions and missing verification, and Oracle synthesizes the final plan with a machine-checkable verification matrix. - Deterministic Checklist Clearance: The interview exits only when a 6-item checklist (objective, scope, acceptance, test strategy, handoff target, no critical gaps) is fully resolved, capped at 5 rounds with carried-forward blockers. - OMX Handoff Contract: Produces a durable plan artifact under .omx/plans/prometheus-strict/ and recommends handoff to $ultragoal or $team only when parallel lanes are justified. - Use Case: Before starting a risky multi-service refactor, run this Skill to pin down scope, non-goals, rollback conditions, and a verification matrix, then hand the approved plan to an execution workflow. ## Quick Start Ask the agent to run prometheus-strict on your goal, for example: plan the migration of the billing service to event-driven architecture before any code changes.

Frequently Asked Questions about prometheus-strict

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

FAQPage Schema
How do I plan a complex coding task before implementation?▼

Invoke prometheus-strict with your goal statement. It runs a Metis interview to clarify requirements, a Momus critique to challenge assumptions, and an Oracle synthesis that outputs a sequenced plan with a verification matrix and handoff recommendation.

What is the difference between Metis, Momus, and Oracle roles?▼

Metis clarifies requirements, constraints, and acceptance criteria through structured questions. Momus adversarially challenges assumptions, scope, and missing verification. Oracle synthesizes the final plan and self-verifies it against machine-checkable acceptance contracts.

When should I not use interview-driven planning?▼

Skip it for clear, low-risk changes that need immediate implementation, simple repository lookups, or post-change QA. The skill is planning-only and explicitly excludes hook implementation, Sisyphus behavior, and direct code edits.

Does prometheus-strict execute code or modify files?▼

No, it is planning-only by default and does not edit source code. It optionally writes a durable plan markdown file under .omx/plans/prometheus-strict/ and hands off execution to $ultragoal or $team when warranted.

How many interview rounds does the planning loop allow?▼

The interview is capped at 5 rounds with a minimum of 2 emitted question rounds when any questions are asked. If clearance is not reached by round 5, unresolved items are carried forward to Oracle as explicit blockers.