PlanForge

What PlanForge does

PlanForge brings structured, spec-driven planning into Hermes. A project is broken into phases with entry and exit criteria, and each phase has XML-structured plans with task dependencies and acceptance criteria. Tasks inside a phase run in waves through Hermes's delegate_task, and a phase must pass a verification gate before the next one starts.

All state lives in a .planning/ folder: PROJECT.md, REQUIREMENTS.md, ROADMAP.md, STATE.md, config.json, and per-phase context, research, plan, summary and verification files. Because it is plain files, it can be version-controlled and moved between tools. Slash commands cover the loop: /planforge-init, /planforge-plan, /planforge-execute, /planforge-verify, /planforge-status and /planforge-ship, which creates a PR from verified work. The plugin registers hooks for commands, pre_tool_call, transform_tool_result and transform_terminal_output, and adds a Roadmap tab to the Hermes web dashboard. Planning can be driven from Telegram, Discord, Slack or the CLI.

Key features

• Phase-based plans with entry and exit criteria and XML task definitions
• Wave execution of parallel tasks through delegate_task
• Verification gate that each phase must pass before proceeding
• File-based state in .planning/ compatible with the GSD format
• Six slash commands from /planforge-init to /planforge-ship
• Roadmap tab in the Hermes web dashboard showing phase progress and blockers

When to use it

• Planning a multi-phase software project and tracing code back to requirements
• Running verified phases from Telegram or Slack while away from the terminal
• Opening a PR from work that passed its verification checks

Who it is for: Developers who use Hermes Agent for larger projects and want written plans, requirements and verification steps.

How it fits with Hermes Agent

Built as a Hermes Agent plugin that uses plugin hooks, delegate_task, the web dashboard and the messaging gateway.

FAQ