docs(prometheus): rewrite AGENTS.md for thin-loader structure
Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent) Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>
This commit is contained in:
YeonGyu-Kim
@@ -1,30 +1,47 @@
|
||||
---
|
||||
name: prometheus-agent
|
||||
description: Developer reference for the Prometheus strategic planner agent — interview flow, plan output format, and key constraints.
|
||||
description: Developer reference for the Prometheus strategic planner agent prompt loaders, prompts-core markdown variants, and model routing.
|
||||
---
|
||||
|
||||
# src/agents/prometheus/ -- Strategic Planner
|
||||
|
||||
**Generated:** 2026-05-15
|
||||
**Generated:** 2026-05-24
|
||||
|
||||
## OVERVIEW
|
||||
|
||||
11 files. Prometheus agent -- interview-mode strategic planner. Reads codebase, questions user, builds detailed work plan before any code is written. Markdown-only output (enforced by `prometheus-md-only` hook).
|
||||
5 TypeScript files plus 3 markdown prompt variants in [`packages/prompts-core/prompts/prometheus/`](file:///Users/yeongyu/local-workspaces/omo/packages/prompts-core/prompts/prometheus/). Prometheus remains the interview-mode strategic planner, but this directory is now a thin adapter layer. Prompt content lives in `packages/prompts-core`; `src/agents/prometheus/` only loads the right markdown variant and applies runtime tool gating.
|
||||
|
||||
This shape follows the package layering refactor in [`ROADMAP.md`](file:///Users/yeongyu/local-workspaces/omo/ROADMAP.md): prompts are harness-neutral core assets, while the OpenCode adapter keeps only model routing and runtime integration.
|
||||
|
||||
## FILES
|
||||
|
||||
| File | Purpose |
|
||||
|------|---------|
|
||||
| `system-prompt.ts` | Composes full system prompt from sections |
|
||||
| `identity-constraints.ts` | FORBIDDEN actions, .md-only enforcement, path restrictions |
|
||||
| `interview-mode.ts` | Interview flow: gather requirements, clarify scope |
|
||||
| `plan-generation.ts` | Plan output structure and validation |
|
||||
| `plan-template.ts` | YAML plan template with task graph, dependencies, waves |
|
||||
| `behavioral-summary.ts` | Behavioral guidelines section |
|
||||
| `high-accuracy-mode.ts` | Enhanced accuracy mode for complex plans |
|
||||
| `gemini.ts` | Gemini-optimized prompt variant |
|
||||
| `gpt.ts` | GPT-optimized prompt variant |
|
||||
| `index.ts` | Barrel exports |
|
||||
| `system-prompt.ts` | Thin loader using `loadPromptSync()` and `prometheusPromptVariants` from `@oh-my-opencode/prompts-core`; exports prompt source routing and disabled-tool filtering |
|
||||
| `gpt.ts` | Thin loader for `PROMETHEUS_GPT_SYSTEM_PROMPT` from `packages/prompts-core/prompts/prometheus/gpt.md` |
|
||||
| `gemini.ts` | Thin loader for `PROMETHEUS_GEMINI_SYSTEM_PROMPT` from `packages/prompts-core/prompts/prometheus/gemini.md` |
|
||||
| `system-prompt.test.ts` | Runtime behavior tests for Question tool filtering |
|
||||
| `prometheus-byte-exactness.test.ts` | Byte-exact sha256 characterization tests for all variants and Question disabled state |
|
||||
| `packages/prompts-core/prompts/prometheus/default.md` | Default/Claude markdown prompt variant |
|
||||
| `packages/prompts-core/prompts/prometheus/gpt.md` | GPT-optimized markdown prompt variant |
|
||||
| `packages/prompts-core/prompts/prometheus/gemini.md` | Gemini-optimized markdown prompt variant |
|
||||
|
||||
## MODEL VARIANT ROUTING
|
||||
|
||||
[`system-prompt.ts`](file:///Users/yeongyu/local-workspaces/omo/src/agents/prometheus/system-prompt.ts) exposes `getPrometheusPromptSource(model)`:
|
||||
|
||||
- GPT family models, as detected by `isGptModel(model)`, route to `"gpt"`.
|
||||
- Gemini family models, as detected by `isGeminiModel(model)`, route to `"gemini"`.
|
||||
- Missing models and all other families route to `"default"`.
|
||||
|
||||
`getPrometheusPrompt(model, disabledTools)` then loads the selected markdown through `loadPromptSync({ source: prometheusPromptVariants[variant], name: "prometheus", variant })` and returns the loaded body.
|
||||
|
||||
## DISABLED TOOL HANDLING
|
||||
|
||||
Prometheus normally includes `Question({ ... })` examples because interview mode uses the Question tool to clarify scope. When the runtime passes `disabledTools` containing `"question"`, `getPrometheusPrompt()` strips fenced TypeScript `Question({ ... })` examples with `QUESTION_TOOL_BLOCK_RE` before returning the prompt.
|
||||
|
||||
This filtering is runtime adapter behavior. Do not duplicate stripped markdown variants in `packages/prompts-core`; keep one source of truth per model family and let `system-prompt.ts` remove Question examples only when the tool is disabled.
|
||||
|
||||
## KEY CONSTRAINTS
|
||||
|
||||
@@ -33,10 +50,12 @@ description: Developer reference for the Prometheus strategic planner agent —
|
||||
- Must explore codebase before planning (NEVER plan blind)
|
||||
- Plans saved to `.omo/plans/`
|
||||
- Acceptance criteria requiring "user manually tests" are FORBIDDEN
|
||||
- Prompt edits belong in [`packages/prompts-core/prompts/prometheus/`](file:///Users/yeongyu/local-workspaces/omo/packages/prompts-core/prompts/prometheus/), not in TypeScript section files
|
||||
|
||||
## PLAN OUTPUT FORMAT
|
||||
|
||||
Plans use YAML with parallel task graph:
|
||||
The markdown variants instruct Prometheus to produce YAML plans with a parallel task graph:
|
||||
|
||||
- Waves (parallel execution groups)
|
||||
- Tasks with dependencies, category, skills
|
||||
- Each task has atomic scope + verification criteria
|
||||
|
||||
Reference in New Issue
Block a user