gormes-planner

Inspect Hermes/Honcho parity evidence and generate executable progress rows.

9|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/TrebuchetDynamics/gormes-agent --skill gormes-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gormes-planner
Source: https://github.com/TrebuchetDynamics/gormes-agent/tree/main/development-skills/gormes-planner
Command: npx skills add https://github.com/TrebuchetDynamics/gormes-agent --skill gormes-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Plan Hermes/Honcho parity and progress-tracking slices from repository evidence, enabling bounded, builder-ready work without runtime code.

Core Features & Use Cases

  • Translate Hermes/Honcho parity findings into concrete progress rows with provenance.
  • Break large parity goals into small, executable units suitable for builders.
  • Centralize references and canonical sources to guide planning decisions.

Quick Start

Inspect Hermes/Honcho parity evidence and generate executable progress rows for a bounded planner pass.

Frequently Asked Questions about gormes-planner

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

FAQPage Schema
How do I map Hermes and Honcho parity gaps into actionable progress rows?

To map Hermes and Honcho parity gaps, inspect repository evidence, parity docs, and progress data to generate bounded, builder-ready progress rows with provenance. This translates findings into executable work units.

What is the best way to break large parity goals into executable units for builders?

The best way to break large parity goals into executable units is to apply planner passes that inspect upstream Hermes and Honcho sources, producing concrete implementation slices suitable for builders.

Do I need access to upstream Hermes and Honcho sources to generate planning artifacts?

Yes, you need access to upstream Hermes and Honcho sources, the feature map, and progress documentation. These references are required to produce executable, testable planning artifacts accurately.

Can I use Codex or Claude agents to drive planner passes for parity tracking?

Yes, you can use Codex, Claude, or other agents to drive planner passes. They inspect repository evidence and parity documentation to generate concrete, testable implementation slices for builders.

Does this planning approach require runtime code execution to track progress?

No, this planning approach does not require runtime code execution. It generates bounded, builder-ready work and progress-tracking slices entirely from static repository evidence and documentation.