momus

Review work plans to identify context gaps and ambiguous requirements.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/jivebreaddev/skills-claude-agent --skill momus-jivebreaddev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: momus
Source: https://github.com/jivebreaddev/skills-claude-agent/tree/main/.claude/skills/momus
Command: npx skills add https://github.com/jivebreaddev/skills-claude-agent --skill momus-jivebreaddev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Momus provides ruthless critique of work plans and implementation plans to catch context gaps, ambiguous requirements, and missing acceptance criteria before execution.

Core Features & Use Cases

  • Detects missing information by simulating implementation steps and flags gaps.
  • Validates presence of references or sources to address gaps; prompts rejection when none provided.
  • Guides reviewers with concrete acceptance criteria and actionable next steps.

Quick Start

Review the provided plan content to identify gaps, check for explicit references, and decide whether to proceed or request clarifications.

Frequently Asked Questions about momus

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a work plan to find ambiguous requirements before execution?

You can identify context gaps in project plans by simulating implementation steps to detect missing information and ambiguous requirements. This method validates explicit references and provides deterministic decision rules to request clarifications.

What are concrete acceptance criteria for rejecting an implementation plan?

Concrete acceptance criteria for rejecting an implementation plan include missing explicit references to address context gaps, failure to pass simulated implementation steps, and lack of actionable next steps when critical information is absent.

How do I evaluate missing information in project roadmaps?

Evaluating missing information in project roadmaps requires rigorous scrutiny of the plan to detect context gaps. It applies deterministic decision rules to check for explicit references and prompts rejection when information is missing.

Does this approach work for design documents or only software implementation plans?

This approach works for both design documents and software implementation plans. It applies rigorous scrutiny to any work plan, detecting context gaps and ambiguous requirements using explicit evaluation criteria and deterministic decision rules.

When should I not use automated plan review for ambiguous requirements?

You should avoid automated plan review when a work plan requires subjective stakeholder negotiation rather than rigorous scrutiny. It is designed to provide deterministic decision rules and actionable next steps for missing information, not to handle subjective ambiguity.