gnd-chart

Organize multi-step work into structured legs with explicit ownership and dispatch order.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert ambiguous goals into bounded, reviewable legs that can be dispatched by gnd-navigate to gnd-diver subagents, reducing planning overhead and misalignment.

Core Features & Use Cases

  • Plan decomposition: Break goals into discrete legs with clear intents and ownership.
  • Deterministic dispatch: Define an explicit, acyclic dispatch order for subagents.
  • Workshop-driven refinement: Support an interactive validation flow where each leg is confirmed before execution.
  • Cross-project applicability: Applicable to any project that uses gnd-navigate/gnd-diver workflow.

Quick Start

Create a plan with LEG-1 as the starting leg and walk through the workshop flow to confirm each leg before dispatch.

Frequently Asked Questions about gnd-chart

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

FAQPage Schema
How do I break down ambiguous project goals into bounded tasks for subagent dispatch?

Structured leg-based planning decomposes ambiguous project goals into discrete legs with explicit ownership and deterministic dispatch order, enabling subagents to execute bounded tasks with clear intents and dependencies.

What is a deterministic dispatch order in multi-step workflow planning?

Deterministic dispatch order is an explicit, acyclic sequence defined during plan decomposition that directs subagents to execute legs in a structured order, preventing execution misalignment and reducing planning overhead.

How do I create a structured plan using leg IDs for subagent workflows?

Start by creating a plan with a designated starting leg such as LEG-1, then walk through the interactive workshop flow to validate and confirm each leg's intent, ownership, and dependencies before dispatch.

Can I apply leg-based planning across different projects using the same workflow?

Leg-based planning is cross-project applicable for any project that uses the gnd-navigate and gnd-diver workflow, transforming user goals into bounded tasks with read-only references and explicit ownership.

Do I need gnd-navigate to dispatch the structured legs created by this planning approach?

Yes, gnd-navigate is required to dispatch the structured legs to gnd-diver subagents, as the planning process specifically generates bounded tasks with leg IDs and dependencies tailored for this dispatch workflow.

What are the limitations of using a workshop-driven flow for plan decomposition?

The workshop-driven approach requires interactive validation to confirm each leg before execution, which adds a manual review step that may slow down fully automated dispatch pipelines for multi-step work.