u/Akolite

I made a new open-source Hermes Agent skill set:

It’s called **Hermes Agent Idea Workflow**.

The goal is to handle the pre-build phase: turning rough ideas into structured design docs, implementation specs, and agent-ready build handoffs before a coding agent starts building.

The basic pipeline is:

rough idea

→ idea-workflow

→ design doc

→ implementation spec

→ agent build handoff

→ spec review

→ Superpowers for GPT

→ implementation planning

→ coding

→ review

→ verification

It includes:

- Lite mode for quick idea capture

- Full mode for serious app/product/tool ideas

- guided interview flow

- reusable question bank

- staged Markdown artifacts

- implementation handoff template

- spec review gate

- PASS / PASS WITH CHANGES / FAIL review model

- `GREENLIGHT NEXT STAGE` override phrase

- generic example handoffs

The idea is not to replace the build workflow. It feeds into one. In my case, the recommended next step is my Superpowers for GPT repo:

I’d love feedback from Hermes users on whether the handoff format is useful for real agent builds.

I made an open-source Markdown skill pack for AI coding agents:

It’s an unofficial Hermes/ChatGPT-compatible adaptation of the Superpowers workflow concepts.

The goal is to give agents reusable procedural workflows for software development instead of relying on one big prompt or hoping the model remembers good engineering habits.

Included workflows:

- task routing

- brainstorming

- implementation planning

- plan execution

- test-driven development

- systematic debugging

- code review

- review feedback handling

- subagent-driven development

- parallel agent dispatch

- git worktrees

- branch finishing

- verification before completion

- writing new skills

Everything is plain Markdown, so it should be easy to inspect, modify, or adapt.

Status: v0.1.0, MIT licensed, 14 skills.

I’d love feedback from people building agent frameworks: should workflow discipline like this be handled as skills, memories, plugins, system prompts, or something else?

I made a small open-source skill pack: **Superpowers for Hermes Agent and ChatGPT**.

Repo:

https://github.com/AkoliteZA/hermes-agent-supwerpowers-chatgpt

The idea is to adapt the Superpowers-style AI coding workflow into explicit Hermes/ChatGPT-compatible skills.

Instead of letting the agent jump straight into coding, the pack gives it reusable workflows for:

- brainstorming before implementation

- writing executable plans

- executing plans step by step

- TDD for behavior changes

- systematic debugging

- requesting and receiving code review

- using git worktrees

- finishing development branches

- verifying before claiming something is done

This is not an official Claude, Anthropic, Hermes, or OpenAI project. It’s an unofficial adaptation/rewrite of the workflow concepts, with the instructions adjusted for Hermes-style skill loading and ChatGPT-style agent sessions.

Current status:

- v0.1.0

- MIT licensed

- 14 Superpowers-prefixed skills

- install-draft/reference copy

- needs real-world smoke testing in Hermes

I’d especially like feedback on:

1. Whether the Hermes install model is clear enough.

2. Whether the skills are too heavy or too light.

3. Which workflows should be trimmed for token efficiency.

4. Whether anyone has a better convention for packaging Hermes skill packs.

If this should wait for a plugin/tool showcase day, happy to repost there instead.