Prometheus Agent
Relevant source files
The following files were used as context for generating this wiki page:
The Prometheus Agent is a specialized strategic planning consultant within the Oh-My-OpenCode ecosystem. Its fundamental identity is that of a Planner, not an implementer. Its primary purpose is to transform user requests into comprehensive, verifiable, and executable work plans stored as Markdown files. Prometheus operates under strict read-only constraints for source code, ensuring that it focus solely on requirements gathering and structural design rather than code execution.
Prometheus follows a multi-phase workflow that includes an initial Interview Mode for requirements gathering, consultation with the Metis Agent for gap analysis, and finally, the generation of a standardized work plan. Once a plan is finalized, Prometheus hands off the execution to other agents, such as Sisyphus, via the /start-work command.
Sources: src/agents/prometheus/identity-constraints.ts:10-30, src/hooks/prometheus-md-only/constants.ts:20-30
Core Identity and Constraints
Prometheus is defined by a set of "Non-Negotiable" absolute constraints that prevent it from performing implementation work. It is strictly a Strategic Consultant.
| Constraint | Description |
|---|---|
| Planner Only | NEVER writes source code or executes implementation commands. |
| Markdown Only | Only permitted to create or edit .md files in specific directories. |
| Path Enforcement | Restricted to .sisyphus/plans/ and .sisyphus/drafts/. |
| Single Plan Mandate | Regardless of task size, all work must be consolidated into one plan. |
| Zero Human Intervention | All verification steps in generated plans must be agent-executable. |
Sources: src/agents/prometheus/identity-constraints.ts:32-150, src/hooks/prometheus-md-only/constants.ts:11-15
Mandatory Workflow
The agent follows a rigid five-step process to ensure plan quality and accuracy:
- Interview: Full consultation to gather requirements and record decisions in drafts.
- Metis Consultation: Pre-generation gap analysis via the Metis agent.
- Plan Generation: Writing the structured plan to the
.sisyphus/plans/directory. - Momus Review: Optional "High Accuracy Mode" where the plan is reviewed by the Momus agent.
- Summary: Presenting the final plan to the user with a guide to
/start-work.
Sources: src/hooks/prometheus-md-only/constants.ts:39-60, src/agents/prometheus/plan-generation.ts:30-50
Phase 1: Interview Mode
Prometheus defaults to an "Interview Mode" where it acts as a consultant to clarify intent. It uses different strategies based on the identified Intent Type.
Intent Classification
Prometheus classifies every request to determine the depth of the interview required:
| Intent Type | signal | primary Focus |
|---|---|---|
| Refactoring | "refactor", "cleanup" | Safety, regression prevention, behavior preservation. |
| Build from Scratch | "create new", "add feature" | Pattern discovery and consistency with existing code. |
| Mid-sized Task | Scoped feature | Boundary definition and "AI-Slop" prevention. |
| Research | "investigate", "look into" | Exit criteria and synthesis of findings. |
| Architecture | "how should we structure" | Strategic trade-offs and mandatory Oracle consultation. |
Sources: src/agents/prometheus/interview-mode.ts:11-30, src/agents/metis.ts:30-45
Data Flow: Interview and Research
During the interview, Prometheus uses background agents (explore and librarian) to gather context before finalizing the technical approach.
Phase 2: Plan Generation
Once all requirements are clear (the "Clearance Checklist" passes), Prometheus transitions to generating a structured work plan.
Metis Consultation
Before writing the actual file, Prometheus must consult Metis. Metis analyzes the interview history to identify hidden intentions, potential over-engineering, and missing acceptance criteria.
Directives for Prometheus from Metis include:
- MUST: Specify exact deliverables.
- MUST: Use agent-executable verification commands (e.g.,
curl,bun test). - MUST NOT: Include criteria requiring human manual testing.
Sources: src/agents/metis.ts:160-200, src/agents/prometheus/plan-generation.ts:60-80
The Plan Template
Generated plans follow a strict Markdown structure defined in the PROMETHEUS_PLAN_TEMPLATE.
- TL;DR: Quick summary, deliverables, and estimated effort.
- Context: Original request, interview summary, and research findings.
- Work Objectives: Core objectives and "Definition of Done".
- Verification Strategy: Mandatory section prohibiting human intervention.
- Execution Strategy: Parallel execution waves and dependency matrices.
- TODOs: Granular tasks including recommended agent profiles (Category/Skills) and reference files.
Sources: src/agents/prometheus/plan-template.ts:15-100
Parallel Execution Logic
Prometheus groups tasks into Waves to maximize throughput. Wave 1 includes tasks with no dependencies, while subsequent waves wait for previous dependencies to complete.
Phase 3: Review and Handoff
Momus Review (High Accuracy Mode)
If the user requests high accuracy, the plan is submitted to Momus, the "ruthless critical reviewer." Momus checks for:
- Reference Validity: Do referenced files and line numbers actually exist?
- Executability: Can a developer (agent) start working without getting stuck?
- Blocking Issues: Identifying contradictions or missing context.
Momus will issue an [OKAY] or [REJECT] verdict. If rejected, Prometheus must fix the issues and iterate.
Sources: src/agents/momus.ts:35-100, src/agents/prometheus/plan-generation.ts:145-160
Final Handoff
After completion, Prometheus performs a cleanup:
- Delete Draft: Removes the working memory file in
.sisyphus/drafts/. - Execution Guidance: Instructs the user to run
/start-workto begin implementation.
Sources: src/agents/prometheus/behavioral-summary.ts:10-30
Summary Table of Agent Components
| Component | Responsibility | Relevant Files |
|---|---|---|
| Identity | Defines read-only status and planner-implementer boundary. | identity-constraints.ts |
| Interview | Strategy for requirements gathering and context research. | interview-mode.ts |
| Metis | Pre-generation consultant identifying gaps and risks. | metis.ts |
| Template | Standardized Markdown structure for work plans. | plan-template.ts |
| Momus | Post-generation reviewer ensuring plan executability. | momus.ts |
Sources: src/agents/prometheus/identity-constraints.ts, src/agents/metis.ts, src/agents/momus.ts
The Prometheus Agent ensures that project implementation is grounded in a rigorous, researched, and verifiable plan, significantly reducing implementation errors and "AI slop" by separating the thinking phase from the doing phase.