gnd-navigate

Dispatch structured plans from .planning/ to gnd-diver subagents and run the integration gate.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/ironloon/peninsular-reveries --skill gnd-navigate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gnd-navigate
Source: https://github.com/ironloon/peninsular-reveries/tree/main/.pi/skills/gnd-navigate
Command: npx skills add https://github.com/ironloon/peninsular-reveries --skill gnd-navigate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This capability enables seamless end-to-end orchestration of planning work by dispatching a structured plan from the .planning/ directory to gnd-diver subagents, handling evaluation, and coordinating delivery.

Core Features & Use Cases

  • Dispatch legs to gnd-diver for execution
  • Review results and apply the integration gate
  • Manage plan resolution and single-session orchestration across multiple legs
  • Sample use case: coordinate a multi-leg plan and deliver the final outcome without manual handoffs.

Quick Start

Use the gnd-navigate skill to resolve the active plan in .planning/ and dispatch all legs to gnd-diver.

Frequently Asked Questions about gnd-navigate

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

FAQPage Schema
How do I orchestrate a multi-leg workflow plan using subagents?

You can orchestrate a multi-leg workflow by dispatching a structured plan from the .planning/ directory to gnd-diver subagents, allowing a single session to resolve the plan, dispatch legs, and coordinate delivery.

What is the best way to execute structured plans without manual handoffs?

Executing structured plans without manual handoffs is achieved by dispatching plan legs to gnd-diver subagents, which reviews results, runs the integration gate, and lands the work within a single orchestration session.

Can I review subagent results and apply an integration gate in one session?

Yes, you can review subagent results and apply an integration gate in a single session by using orchestration to evaluate dispatched legs from gnd-diver before landing the final work.

How does plan resolution work for dispatching tasks to subagents?

Plan resolution works by reading a structured plan from the .planning/ directory, breaking it into individual legs, and dispatching those legs to gnd-diver subagents for end-to-end execution.

Do I need a .planning/ directory to coordinate subagent orchestration?

Yes, you need a .planning/ directory because the orchestration process resolves the active structured plan directly from that location to dispatch legs to gnd-diver subagents.

When should I use subagent orchestration for workflow planning?

You should use subagent orchestration for workflow planning when you have a structured multi-leg plan that requires automated dispatch, result review, integration gating, and final delivery without manual intervention.