oh-my-codex (Yeachan-Heo) — Prompts
Verbatim Excerpt 1: deep-interview/SKILL.md (Ambiguity Gating)
Prompting technique: Socratic gating with quantitative ambiguity scoring; single-question-per-round discipline; source classification taxonomy
<Execution_Policy>
- Ask ONE question per round (never batch multiple interview rounds into one `questions[]` form)
- Ask about intent and boundaries before implementation detail
- Target the weakest clarity dimension each round after applying the stage-priority rules below
- Treat every answer as a claim to pressure-test before moving on: the next question should usually demand evidence or examples, expose a hidden assumption, force a tradeoff or boundary, or reframe root cause vs symptom
- Do not rotate to a new clarity dimension just for coverage when the current answer is still vague; stay on the same thread until one layer deeper, one assumption clearer, or one boundary tighter
- Before crystallizing, complete at least one explicit pressure pass that revisits an earlier answer with a deeper, assumption-focused, or tradeoff-focused follow-up
- Gather codebase facts via `explore` before asking user about internals
- Route facts before judgment in the Ouroboros style: before presenting a user-facing interview round, classify whether the needed information is a discoverable fact, a fact needing confirmation, or a human decision.
</Execution_Policy>
Source classification labels:
- `[from-code][auto-confirmed]` — exact, high-confidence codebase facts
- `[from-code]` — inferred codebase findings needing confirmation
- `[from-research]` — externally sourced facts; facts only, not decisions
- `[from-user]` — goals, preferences, business logic, scope, non-goals, acceptance criteria
Verbatim Excerpt 2: ultragoal/SKILL.md (Durable Goal Loop)
Prompting technique: Procedural loop with explicit state commands; ledger-anchored checkpoint discipline; steering invariants
## Complete goals
Loop until `omx ultragoal status` reports all goals complete:
1. Run `omx ultragoal complete-goals`.
2. Read the printed handoff.
3. Call `get_goal`.
4. If no active Codex goal exists, call `create_goal` with the printed payload. In aggregate mode, if the same aggregate Codex objective is already active, continue the current OMX story without creating a new Codex goal.
5. Complete the current OMX story only.
6. Run a completion audit against the story objective and real artifacts/tests.
7. In aggregate mode, do **not** call `update_goal` for intermediate stories; checkpoint with a fresh `get_goal` snapshot whose aggregate objective is still `active`. On the final story only, first run the mandatory final cleanup/review gate below; call `update_goal({status: "complete"})` only after that gate is clean.
Verbatim Excerpt 3: team/SKILL.md (tmux Worker Coordination)
Prompting technique: Operational contract with hard error conditions; worker CLI routing via env vars; state-file protocol
When user triggers `$team`, the agent must:
1. Invoke OMX runtime directly with `omx team ...`
2. Avoid replacing the flow with in-process `spawn_agent` fanout
3. Verify startup and surface concrete state/pane evidence
4. If active team mode state is missing, initialize/sync it from canonical team runtime state before proceeding
5. Keep team state alive until workers are terminal (unless explicit abort)
6. Handle cleanup and stale-pane recovery when needed
If `omx team` is unavailable, stop with a hard error.