Ultrawork Mode & Boulder Loop
Relevant source files
The following files were used as context for generating this wiki page:
Ultrawork Mode and the Boulder Loop represent the project's high-intensity orchestration and planning framework designed to ensure rigorous software engineering practices. At its core, this system separates strategic planning from tactical execution. "Prometheus" serves as the strategic planner, while "Sisyphus" and "Hephaestus" act as the executors who carry the "boulder" of implementation tasks. The framework enforces strict identity constraints, ensuring that planners never write code and executors follow verified, multi-step work plans.
Sources: src/hooks/keyword-detector/ultrawork/planner.ts:1-15, src/agents/prometheus/identity-constraints.ts:10-25
Ultrawork Mode for Planners
Ultrawork Mode specifically configures the Prometheus agent to operate as a Strategic Planning Consultant. In this mode, the agent is strictly prohibited from implementing code, running implementation commands, or creating non-markdown files. Its primary output is limited to requirements gathering and the generation of structured work plans saved in .sisyphus/plans/.
Sources: src/agents/prometheus/identity-constraints.ts:27-50, src/hooks/keyword-detector/ultrawork/planner.ts:5-20
Identity and Tool Restrictions
Under Ultrawork Mode, the planner's identity is defined by a "Planning ≠ Doing" philosophy. Any request to "do" or "fix" something is automatically re-interpreted as a request to "create a work plan" for that action.
| Tool | Status | Constraint |
|---|---|---|
| Write/Edit | Restricted | Allowed ONLY for .sisyphus/**/*.md |
| Read | Allowed | All files accessible for context gathering |
| Bash | Restricted | Research/Grep commands only; implementation commands blocked |
| task | Allowed | Restricted to explore and librarian agents |
Sources: src/hooks/keyword-detector/ultrawork/planner.ts:22-30, src/agents/prometheus/identity-constraints.ts:52-70
The Planning Workflow
The planner follows a mandatory context-gathering protocol before drafting any plan. This ensures that the generated work plan is "bulletproof" and grounded in existing codebase patterns.
The flow demonstrates the mandatory context gathering required before plan generation.
Sources: src/hooks/keyword-detector/ultrawork/planner.ts:35-50, src/agents/prometheus/plan-generation.ts:38-65
The Boulder Loop: Plan Generation and Review
The "Boulder Loop" refers to the iterative process of generating, reviewing, and refining implementation plans before execution begins. It involves a sequence of specialized agents to ensure technical accuracy and completeness.
Phase 1: Metis Consultation
Before the final work plan is written, the system triggers a mandatory consultation with "Metis" for gap analysis. Metis identifies missing acceptance criteria, edge cases, and potential scope creep.
Sources: src/agents/prometheus/plan-generation.ts:80-110
Phase 2: Momus Review (The High Accuracy Review)
Once a plan is generated, the user can opt for a "High Accuracy Review" via the Momus agent. Named after the god of mockery, Momus is a ruthless critic that identifies blockers, invalid file references, and ambiguities.
| Momus Verdict | Meaning | Result |
|---|---|---|
| OKAY | Plan is executable | Proceed to /start-work |
| REJECT | Blocking issues found | Planner must fix top 3 issues and resubmit |
Sources: src/agents/momus.ts:35-60, src/agents/prometheus/plan-generation.ts:165-185
Verification Logic in Momus
Momus operates with a specific "Approval Bias," focusing only on Blocking Issues rather than perfectionism.
This diagram illustrates the review cycle between the planner and the reviewer before the implementation phase.
Sources: src/agents/momus.ts:100-140, src/agents/prometheus/plan-generation.ts:187-200
Work Plan Structure
The Boulder Loop produces a highly structured markdown file that acts as the "boulder" to be pushed by execution agents.
Mandatory Plan Components
- Parallel Execution Waves: Tasks are grouped into waves (Wave 1, Wave 2, etc.) based on dependency analysis to maximize execution speed.
- Dependency Matrix: A table mapping which tasks block or depend on others.
- Agent-Executed QA Scenarios: Every task must have a verifiable scenario that an agent can run (e.g., Playwright for UI, curl for APIs) without human intervention.
- Recommended Agent Profiles: Each task specifies a
category(e.g.,ultrabrain,visual-engineering) and requiredskills.
Sources: src/agents/prometheus/plan-template.ts:15-60, src/hooks/keyword-detector/ultrawork/planner.ts:70-95
Execution Profiles
| Category | Model Used | Ideal For |
|---|---|---|
ultrabrain | GPT-5.3 Codex (XHigh) | Complex architecture, logic-heavy tasks |
visual-engineering | Gemini-3 Pro | UI/UX, animations, frontend styling |
deep | GPT-5.3 Codex (Medium) | Goal-oriented autonomous problem solving |
quick | Claude-Haiku-4-5 | Trivial fixes, single file changes |
Sources: src/tools/delegate-task/constants.ts:135-150, sisyphus-prompt.md:15-30
Execution Discipline: The Todo System
Once planning is complete, the "boulder" is moved through the implementation phase using strict Todo/Task Discipline. This ensures real-time visibility and recovery.
Implementation Workflow
- Task Start: Use
todowriteorTaskCreateimmediately upon receiving a request. - Step Progress: Mark a single task as
in_progressbefore acting. - Completion: Mark
completedimmediately after verification. Batch-completing tasks is considered a blocking anti-pattern.
Sources: src/agents/hephaestus.ts:25-50, src/agents/sisyphus.ts:35-65
The execution loop defines how implementations are tracked and verified step-by-step.
Sources: src/agents/hephaestus.ts:190-210, sisyphus-prompt.md:250-280
Summary
The Ultrawork Mode and Boulder Loop create a robust engineering ecosystem where complexity is managed through rigid separation of concerns. By forcing the Prometheus planner into a restricted markdown-only environment, the project ensures that implementation is always preceded by strategic thought. The Momus review cycle and the subsequent parallelized execution waves handled by Sisyphus or Hephaestus guarantee that work is not only planned but also verified through automated QA scenarios, eliminating the need for human intervention in the implementation feedback loop.