Love archon!
I was trying to make something like it on my own, but this is so much better.
One thing that could be useful is to give the user customizable Containers (Module / System / Epic / Feature / etc...) with rules for what work item types can be inside them. Then custom work item types (Build, Test, Integrate, Bug, etc...). Also with assignable workflows. The requirement for knowledge, RAG, all archon features could be assigned at either the work item, container, or
A big issue I'm noticing is that no matter the tool / OS / MCP server, nearly every coding assistant fails badly at relating the tasks to one another, or a wider set of tasks, or stop paying attention to the order of those tasks after starting. They will race down the rabbit hole on a single task to show the user how completeness-oriented they can be. Short of retraining our own models, it's something that 90% of people have to build around at the tool or MCP level, like what Archon offers.
Hooks could work for claude code based on an MCP pre-tool or postooluse matcher on something like advance_workitem_step, (if there were work item types that had steps or subtasks, or if those work item types had specific workflows assigned to them, configurable by the user in the UI). It could then force claude to have all fields filled, or to go through certain workflows. The vector DB could be used to track or enhance these relationships by container or temporally, or by code dependency.
That was the system I was building, but it's nowhere near the capabilities and functionality of Archon. I do still notice though that claude will get confused and forget the right workflow, even with an archon task that comes from a very well designed / decomposed PRP.
Love this new Archon though, a truly masterful creation
Love archon!
I was trying to make something like it on my own, but this is so much better.
One thing that could be useful is to give the user customizable Containers (Module / System / Epic / Feature / etc...) with rules for what work item types can be inside them. Then custom work item types (Build, Test, Integrate, Bug, etc...). Also with assignable workflows. The requirement for knowledge, RAG, all archon features could be assigned at either the work item, container, or
A big issue I'm noticing is that no matter the tool / OS / MCP server, nearly every coding assistant fails badly at relating the tasks to one another, or a wider set of tasks, or stop paying attention to the order of those tasks after starting. They will race down the rabbit hole on a single task to show the user how completeness-oriented they can be. Short of retraining our own models, it's something that 90% of people have to build around at the tool or MCP level, like what Archon offers.
Hooks could work for claude code based on an MCP pre-tool or postooluse matcher on something like advance_workitem_step, (if there were work item types that had steps or subtasks, or if those work item types had specific workflows assigned to them, configurable by the user in the UI). It could then force claude to have all fields filled, or to go through certain workflows. The vector DB could be used to track or enhance these relationships by container or temporally, or by code dependency.
That was the system I was building, but it's nowhere near the capabilities and functionality of Archon. I do still notice though that claude will get confused and forget the right workflow, even with an archon task that comes from a very well designed / decomposed PRP.
Love this new Archon though, a truly masterful creation