That's fair, the PRD example is pretty cool but not the best - I have a few workflows that I use myself for doing bug bounties and deep research, but they are a bit much.
The current examples were mostly to show how you could set up different phases and how agents can work in parallel in different phases while still keeping some structure - basically any problem that you could define the logical phases in the way for solving it is going to work great with Hephaestus.
Soon I'll release a few more examples and a few tools that would make Hephaestus a development tool that learns about your repo as time goes and able to fix and add features for your code base
Hey,
This is just a very first version of Hephaestus that is only a month in a work to showcase the idea of an autonomous agent orchestration. As we speak I'm building on top of it a development tool that would learn your codebase as time goes on, which is hopefully going to result in faster development.
Although do note that Hephaestus is not only for development purposes, it's supposed to be an agnetic framework for building workflows - such as a research workflow, investment workflow and so on, based on the semi-structured phases principles.
Also - everything is forever going to be open source (including the future features and development tools), so look out :)
I've been working on Hephaestus - an open-source framework that changes how we think about AI agent workflows.
The Problem: Most agentic frameworks make you define every step upfront. But complex tasks don't work like that - you discover what needs to be done as you go.
The Solution: Semi-structured workflows. You define phases - the logical steps needed to solve a problem (like "Reconnaissance → Investigation → Validation" for pentesting). Then agents dynamically create tasks across these phases based on what they discover.
Example: During a pentest, a validation agent finds an IDOR vulnerability that exposes API keys. Instead of being stuck in validation, it spawns a new reconnaissance task: "Enumerate internal APIs using these keys." Another agent picks it up, discovers admin endpoints, chains discoveries together, and the workflow branches naturally.
Agents share discoveries through RAG-powered memory and coordinate via a Kanban board. A Guardian agent continuously tracks each agent's behavior and trajectory, steering them in real-time to stay focused on their tasks and prevent drift.
Fair warning: This is a brand new framework I built alone, so expect rough edges and issues. The repo is a bit of a mess right now. If you find any problems, please report them - feedback is very welcome! And if you want to contribute, I'll be more than happy to review it!
The current examples were mostly to show how you could set up different phases and how agents can work in parallel in different phases while still keeping some structure - basically any problem that you could define the logical phases in the way for solving it is going to work great with Hephaestus.
Soon I'll release a few more examples and a few tools that would make Hephaestus a development tool that learns about your repo as time goes and able to fix and add features for your code base