Momus Agent

{
  "model": "gpt-5.2",
  "variant": "medium",
  "temperature": 0.1,
  "reasoningEffort": "medium",
  "textVerbosity": "high"
}

{
  "model": "claude-opus-4-6",
  "variant": "max",
  "temperature": 0.1,
  "thinking": {
    "type": "enabled",
    "budgetTokens": 32000
  }
}

{
  "model": "gemini-3.1-pro",
  "variant": "high",
  "temperature": 0.1
}

**[OKAY]**

**Summary**: Plan is executable. All references verified, tasks have sufficient context to begin.

**[REJECT]**

**Summary**: Plan has blocking issues that prevent execution.

**Blocking Issues** (max 3):
1. **Task 3: Missing reference file**
   - References `src/services/auth.ts` but file doesn't exist
   - Fix: Verify file path or remove reference
   
2. **Task 5: Insufficient context**
   - Says "implement feature" with no description, files, or starting point
   - Fix: Add file location and brief implementation approach
   
3. **Tasks 2 and 4: Contradictory requirements**
   - Task 2 says "use JWT tokens", Task 4 says "use session cookies"
   - Fix: Clarify authentication method

task(
  subagent_type="momus",
  description="Review authentication implementation plan",
  prompt="Review .sisyphus/plans/auth-implementation.md"
)

// Momus response:
"**[OKAY]**

**Summary**: Plan is executable and well-structured. All 8 referenced files verified to exist and contain relevant patterns. Each task has clear starting point and enough context to begin implementation.

Verified references:
- `src/server.ts:15-30` - Express middleware pattern ✓
- `src/middleware/error-handler.ts` - Error handling pattern ✓
- `src/config/database.ts` - Database connection ✓
- All other references checked and valid ✓

Executability check:
- Task 1 (JWT setup): Clear dependencies and file locations ✓
- Task 2 (Password hashing): Specific bcrypt configuration ✓
- Task 3 (Auth middleware): Pattern reference provided ✓
- Task 4 (Register endpoint): Route structure defined ✓
- Task 5 (Login endpoint): Complete flow outlined ✓

A capable developer can execute this plan without getting stuck."

task(
  subagent_type="momus",
  description="Review refactoring plan",
  prompt="Review .sisyphus/plans/refactor-auth.md"
)

// Momus response:
"**[REJECT]**

**Summary**: Plan has 2 blocking issues - referenced files don't exist or don't contain claimed content.

**Blocking Issues**:

1. **Task 2: Non-existent reference file**
   - References `src/utils/token-generator.ts` as pattern to follow
   - File does not exist (verified with read)
   - Fix: Update reference to actual file, or remove if not needed

2. **Task 4: Incorrect reference content**
   - Says "follow error handling pattern from `src/middleware/auth.ts:45-60`"
   - Lines 45-60 contain JWT validation code, not error handling
   - Error handling is actually at lines 80-95
   - Fix: Update line numbers to 80-95

3. **Task 6: Zero context**
   - Says "Implement refresh token logic" with no details
   - No file location, no pattern reference, no description
   - Developer has no starting point
   - Fix: Add file location and basic approach (e.g., "Add refreshToken field to users table, create /api/auth/refresh endpoint")"

task(
  subagent_type="momus",
  description="Review microservices architecture plan",
  prompt="Review .sisyphus/plans/microservices-setup.md"
)

// Momus response:
"**[REJECT]**

**Summary**: Plan contains contradictory requirements that make implementation impossible.

**Blocking Issues**:

1. **Tasks 2 and 5: Authentication method contradiction**
   - Task 2: "Implement JWT authentication for stateless services"
   - Task 5: "Set up Redis session store for user sessions"
   - These are mutually exclusive approaches
   - Fix: Choose one method (JWT = stateless, Redis sessions = stateful)

2. **Tasks 3 and 7: Database contradiction**
   - Task 3: "Use PostgreSQL for user service"
   - Task 7: "Migrate user data from PostgreSQL to MongoDB"
   - Can't use and migrate away from same database
   - Fix: Clarify database strategy - use Postgres OR migrate to Mongo, not both

3. **Task 4: Impossible requirement**
   - Says "Deploy services to both AWS ECS and Google Cloud Run simultaneously"
   - Plan provides no multi-cloud deployment strategy
   - No context on why both platforms needed
   - Fix: Choose primary platform, or add multi-cloud deployment section"

task(
  subagent_type="momus",
  description="Review API endpoint addition plan",
  prompt="Review .sisyphus/plans/add-search-endpoint.md"
)

// Momus response:
"**[OKAY]**

**Summary**: Plan is executable despite minor imperfections. All references valid, tasks have starting points.

Minor observations (NOT blockers, not requiring changes):
- Task 3 acceptance criteria could be more specific about edge cases
- Task 5 doesn't mention rate limiting (but not required for basic implementation)
- Error handling approach is basic (but functional and improvable later)

Why OKAY despite these:
- All observations are "could be better" not "cannot execute"
- Developer can figure out edge cases during implementation
- Rate limiting can be added later if needed
- Basic error handling is sufficient to start

Plan meets the "80% clear" threshold. Developer won't get stuck."

{
  "agents": {
    "momus": {
      "model": "openai/gpt-5.2",
      "variant": "medium",
      "temperature": 0.1,
      "reasoningEffort": "medium",
      "textVerbosity": "high",
      "prompt_append": "Additional review guidelines...",
      "disable": false
    }
  }
}