meridian

Route user requests to specialized subskills with auditable context handoffs.

5|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/KodingDev/meridian --skill meridian-kodingdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meridian
Source: https://github.com/KodingDev/meridian/tree/main/skills/meridian
Command: npx skills add https://github.com/KodingDev/meridian --skill meridian-kodingdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Route user requests to the correct subskill and govern subagent reasoning to maintain context hygiene. The routing framework enforces disciplined handoffs, prevents leakage of internal reasoning, and keeps session context auditable.

Core Features & Use Cases

  • Routing signals to specialized subskills (brainstorm, execute, debug, review, research, respond, delegate) based on task requirements.
  • Subagent context hygiene and knowledge capture to prevent stale or leaked reasoning across turns.
  • Governance mechanisms, including the Meridian auto modifier and specialist lenses, to maintain quality and safety across complex sessions.
  • Use cases include coordinating end-to-end feature work, debugging sessions with subagents, and ensuring consistent documentation.

Quick Start

Assess a user request and route it to the appropriate subskill using Meridian's routing rules.

Frequently Asked Questions about meridian

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

FAQPage Schema
How do I route tasks to subagents without leaking internal reasoning?

Subagent routing prevents reasoning leakage by enforcing disciplined handoffs and maintaining context hygiene. Governance mechanisms define gating signals and routing tables to ensure safe, auditable task delegation across specialized subskills.

What is research-first orchestration for workflow management?

Research-first orchestration is a routing framework that governs subagent reasoning and delegates tasks to specialized subskills. It maintains session context hygiene by preventing stale reasoning and ensuring structured documentation across complex workflows.

How do I maintain context hygiene across complex subagent sessions?

Context hygiene is maintained through governance mechanisms that prevent stale or leaked reasoning across turns. The routing framework enforces disciplined handoffs, keeping session context auditable and preventing internal reasoning from contaminating subsequent tasks.

Can I use automated routing signals for debugging sessions with subagents?

Yes, automated routing signals can direct debugging sessions to specialized subskills. The Meridian auto modifier integrates with routing rules to assess requests and trigger safe, auditable handoffs to the appropriate debug or execute subskill.

What's the best way to orchestrate end-to-end feature work with multiple subagents?

Orchestrating end-to-end feature work requires a routing framework that delegates tasks to specialized subskills like brainstorm, execute, and review. Disciplined handoffs and knowledge capture ensure consistent documentation and prevent context leakage.

Why does stale subagent reasoning leak into my session context?

Stale reasoning leaks when subagent handoffs lack disciplined governance. The routing framework prevents this by defining gating signals and routing tables that enforce context hygiene, ensuring internal reasoning does not bleed across turns or subskills.