metis

Name: metis
Availability: InStock
Author: jivebreaddev

Analyze planning sessions to identify missing questions, guardrails, and scope risks.

Updated Feb 5, 2026

Search Tags:#requirements #scope #risk-management #pre-implementation #guardrails #analysis-framework #planning-analysis

Ready to run

npx skills add https://github.com/jivebreaddev/skills-claude-agent --skill metis-jivebreaddev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: metis
Source: https://github.com/jivebreaddev/skills-claude-agent/tree/main/.claude/skills/metis
Command: npx skills add https://github.com/jivebreaddev/skills-claude-agent --skill metis-jivebreaddev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Use when reviewing plans, specs, or requirements before implementation to catch missing questions, undefined guardrails, unvalidated assumptions, and scope risks.

Core Features & Use Cases

Structured pre-implementation analysis to identify gaps and risks.
Frameworks for evaluating requirements, assumptions, scope, dependencies, and success criteria.
Practical guidance with test scenarios to surface edge cases and guardrails.

Quick Start

Analyze a plan to surface questions, guardrails, and assumptions and generate actionable recommendations.

Frequently Asked Questions about metis

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

FAQPage Schema

How do I identify missing requirements and scope risks before implementation?▼

Pre-implementation analysis identifies missing requirements and scope risks by evaluating planning sessions to surface gaps, undefined guardrails, and invalid assumptions. This structured review process generates actionable recommendations to validate project scope before development begins.

What is pre-implementation planning with guardrail checks?▼

Pre-implementation planning with guardrail checks is a formal analysis framework that evaluates requirements, dependencies, and success criteria. It reviews plans and specs to catch unvalidated assumptions and scope risks, providing structured outputs that surface gaps and acceptance criteria.

How do I validate unvalidated assumptions in a project plan?▼

Validating unvalidated assumptions requires a formal analysis framework to review planning sessions and requirements. The process evaluates specs to identify undefined guardrails, missing questions, and scope risks, generating structured outputs with dependencies and acceptance criteria.

Does pre-implementation analysis work for software and product initiatives?▼

Pre-implementation analysis is applicable across product, software, and project initiatives. The framework evaluates requirements, assumptions, scope, dependencies, and success criteria using test scenarios to surface edge cases and guardrails for diverse project types.

What is the best way to review project specs for edge cases and dependencies?▼

Reviewing project specs for edge cases and dependencies uses a structured analysis framework with test scenarios. This pre-implementation approach evaluates requirements and assumptions to surface gaps, guardrails, and risks, generating actionable recommendations and acceptance criteria.

When do I need requirements validation and plan reviews?▼

Requirements validation and plan reviews are needed when evaluating plans, specs, or requirements before implementation. Use pre-implementation analysis to catch missing questions, undefined guardrails, unvalidated assumptions, and scope risks across product or software initiatives.