Does this skill require a separate server?

Yes, this skill is designed to work alongside the Metis MCP server, providing the methodology and judgment while the server handles the technical execution.

How does Metis handle ad-hoc work like bugs?

Ad-hoc work is captured in a dedicated Backlog document type, categorized as bug, feature, or tech-debt, and can be pulled into active initiatives when capacity allows.

What is the Flight Levels methodology in Metis?

Flight Levels is a management framework that connects operational work (tasks) to strategic goals (vision) through different levels of abstraction to ensure organizational alignment.

Why does Metis use the filesystem as the source of truth?

Using the filesystem ensures that project documentation lives alongside the code, is version-controlled, and remains accessible without external database dependencies.

What are the core document types in Metis?

The hierarchy consists of Vision (North Star), Strategy (approach), Initiative (capability increments), and Task (atomic units), plus Backlogs and ADRs.

Metis Flight Levels

Name: Metis Flight Levels
Author: colliery-io

bycolliery-io

•

Productivity & Workflow

Implements the Flight Levels methodology to align project vision with daily tasks using a hierarchical, Kanban-based pull system.

About

Metis is a strategic work management skill that guides users through the Flight Levels methodology, bridging the gap between high-level vision and technical execution. It extends the Metis MCP server by providing expert judgment on work decomposition, document selection, and phase transitions. By enforcing a strict hierarchy (Vision to Strategy to Initiative to Task) and a pull-based Kanban system, Metis ensures that all development effort is aligned with core objectives while preventing common productivity killers like excessive work-in-progress or shadow backlogs. It is ideal for teams needing structured, filesystem-based project documentation and clear strategic alignment.

Key Features

Pull-based Kanban system to manage capacity and workflow
Phase-gated progress monitoring with explicit exit criteria
1 GitHub stars
Hierarchical alignment from high-level Vision to atomic Tasks
Methodology guidance for effective work decomposition and sizing
Pre-defined project patterns for greenfield work, tech debt, and incidents

Use Cases

Establishing a single source of truth for project documentation directly in the filesystem
Decomposing large project visions into manageable, prioritized initiatives and tasks
Managing technical debt through structured campaigns that trace back to strategic goals

About

Key Features

Pull-based Kanban system to manage capacity and workflow
Phase-gated progress monitoring with explicit exit criteria
1 GitHub stars
Hierarchical alignment from high-level Vision to atomic Tasks
Methodology guidance for effective work decomposition and sizing
Pre-defined project patterns for greenfield work, tech debt, and incidents

Use Cases

Establishing a single source of truth for project documentation directly in the filesystem
Decomposing large project visions into manageable, prioritized initiatives and tasks
Managing technical debt through structured campaigns that trace back to strategic goals