metis

Analyzes plans and requests to identify gaps, risks, and hidden requirements before planning.

1|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/UtsavBalar1231/oh-my-claudeagent --skill metis-utsavbalar1231
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metis
Source: https://github.com/UtsavBalar1231/oh-my-claudeagent/tree/main/skills/metis
Command: npx skills add https://github.com/UtsavBalar1231/oh-my-claudeagent --skill metis-utsavbalar1231

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Draft plans and feature requests often contain hidden assumptions, undefined scope boundaries, and overlooked risks that only surface during implementation. This Skill performs pre-planning gap analysis so those issues are caught before a planner commits to an approach. ## Core Features & Use Cases - Plan File Analysis: Point it at a draft plan file (for example a Status: DRAFT plan from prometheus) and it reads and gap-analyzes the contents. - Inline Request Analysis: Pass any free-text request and it treats the text itself as the subject, classifying intent and exploring the codebase for relevant patterns. - Structured Output: Produces analysis covering hidden intentions, scope boundaries and gaps, risk factors, technical constraints, and actionable directives that feed directly into the prometheus planner. - Use Case: Before finalizing a plan to refactor an authentication module, run this Skill on the draft plan to surface missing edge cases, unstated dependencies, and risk factors the planner should address. ## Quick Start Ask the assistant to run the metis analysis on your draft plan file or on a written feature request to identify gaps and risks before planning.

Frequently Asked Questions about metis

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

FAQPage Schema
How do I analyze a draft plan for gaps and risks?

Pass the plan file path as the argument and the Skill reads the file, classifies intent, explores the codebase for related patterns, and returns structured analysis covering gaps, risks, and planner directives.

Can I analyze a feature request without a plan file?

Yes. Any argument that does not resolve to a readable file is treated as an inline request, and the request text itself is gap-analyzed. If nothing is provided, the Skill asks what to analyze.

What does the metis analysis output include?

The output is a structured analysis covering hidden intentions, scope boundaries and gaps, risk factors, technical constraints, and actionable directives. It is designed to feed directly into the prometheus planning step.

When should I run pre-planning analysis in my workflow?

Run it after a draft plan exists but before the planner finalizes it, or on a raw request before any planning begins. It is not a replacement for planning or execution; it only vets inputs to those stages.

What are the limitations of automated plan gap analysis?

The analysis depends on what is written in the plan or request and what patterns exist in the codebase, so unstated business context outside the repository may be missed. Treat its directives as input to planner judgment, not final decisions.