Review plans and specs to identify gaps, ambiguities, and missing context.
npx skills add https://github.com/masrurimz/amp-sisyphus --skill momus
Please help me install this Agent Skill. Skill: momus Source: https://github.com/masrurimz/amp-sisyphus/tree/main/skills/momus Command: npx skills add https://github.com/masrurimz/amp-sisyphus --skill momus
This Skill provides a ruthless, read-only review of plans, specs, and designs to identify gaps, ambiguities, and missing context before implementation, reducing risk and costly rework.
To begin, prompt Momus to review the target plan document, for example: "Review the Prometheus design spec for feature X and identify gaps, ambiguities, and missing context."
High-intent search queries and answers about installing and using this skill.
To review a design spec for gaps and missing context, you can prompt a ruthlessly critical read-only critique of your implementation specs and architectural designs to identify ambiguities and surface edge cases through mental simulation before any code is written.
The best way to catch edge cases in software engineering plans is to perform a ruthless design review that mentally simulates outcomes against project goals, surfacing hidden assumptions and dependencies while documenting issues with severity labels.
Yes, you can review Prometheus plans without modifying source files because this approach provides a strictly read-only critique, ensuring your design documents and implementation specs remain untouched while receiving structured feedback.
No, design review for risk assessment does not require writing to the project repository. It performs read-only analysis of your plans and specs, delivering actionable fixes and severity labels without altering any source files.
To get structured feedback for architectural decisions and engineering tasks, run a critical plan review that evaluates clarity, verifiability, and completeness, outputting documented issues with concrete fixes aligned with your big-picture project goals.
A limitation of read-only critique for implementation specs is that it only identifies gaps and missing context without applying fixes, meaning you must manually resolve the documented ambiguities and edge cases in your source files afterward.
B0yZ4kr14Review specification and implementation plan for product fit and engineering risk.
d0whc3rReviews code across correctness, readability, architecture, security, and performance with severity-labeled findings.
ckyeonGenerate a Product Requirements Document from conversation context and submit it to the issue tracker.
TeiNamAutomate Laravel project verification for CI/CD pipelines.
