momus

Review work plans for missing context, acceptance criteria, and ambiguous requirements.

25|1|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/toongri/oh-my-toong-playground --skill momus-toongri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: momus
Source: https://github.com/toongri/oh-my-toong-playground/tree/main/skills/momus
Command: npx skills add https://github.com/toongri/oh-my-toong-playground --skill momus-toongri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Complex work plans often skip context, leave acceptance criteria vague, or reference files that may not exist, resulting in stalled implementations and avoidable rework.

Core Features & Use Cases

  • Pre-commit Predictions & Simulation: Record 3-5 high-risk areas before fully reading the plan, then simulate each task step to surface ambiguities, MECE violations, and missing atomicity.
  • Reference Verification & Pre-Mortem: Confirm that referenced files exist or are specific enough, and generate failure scenarios that plans must defend against before approval.
  • Use Case: Apply this review to feature, migration, or refactor plans to validate that the execution strategy is fully documented and the verdict follows the APPROVE/REQUEST_CHANGES/COMMENT structure driven by certainty-tagged findings.

Quick Start

Review the attached feature plan for missing acceptance criteria, ambiguous requirements, and unreferenced files before approval.

Frequently Asked Questions about momus

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

FAQPage Schema
How do I catch missing context and ambiguous requirements in a work plan before implementation?

A pre-mortem review for implementation readiness identifies blocking gaps by critically analyzing work plans for missing context, vague acceptance criteria, and unreferenced files. It generates failure scenarios and certainty-tagged findings that the plan must defend against before approval.

How do I verify referenced files exist in a migration plan?

To verify referenced files exist in a migration plan, the review process confirms that all referenced files are present or specified clearly enough before execution begins. This reference verification ensures downstream implementation tasks do not stall due to missing dependencies.

Can I use simulation protocols to surface MECE violations in a refactor plan?

Yes, you can use simulation protocols to surface MECE violations in a refactor plan by simulating each task step. This surfaces ambiguities, missing atomicity, and high-risk areas before fully reading the plan, generating pre-mortem failure scenarios that drive final approval verdicts.

What is the best way to review feature plans for missing acceptance criteria?

The best way to review feature plans for missing acceptance criteria is applying a critical review framework that tags findings by certainty. This validates that the execution strategy is fully documented and outputs structured APPROVE, REQUEST_CHANGES, or COMMENT verdicts backed by specific evidence.