| ▲ | cschneid 3 hours ago | |
Can this take vague ideas, do iterative design with me, and breakdown tasks to then pass off to agents to build? I was playing with a very similar project recently that was more focused on a high level input ("Build a new whatever dashboard, <more braindump>") and went back and forth with an agent to clarify and refine. Then broke down into Epics/Stories/Tasks, and then handed those off automatically to build. The workflow then is iterating on those high level requests. Heavily inspired by the dark factory posts that have been making the rounds recently. From a glance, it seems like this is designed so that I write all the tasks myself? Does it have any sort of coordination layer to manage git, or otherwise keep agents from stepping on each other? | ||
| ▲ | bumpyclock 3 hours ago | parent | next [-] | |
I've been working on a similar project https://github.com/BumpyClock/tasque . Tracks tasks (Epics, tasks, subtasks) with deps between them. So I plan for an hour or so and then when I walk away from my desk I had the tasks for the agents to code and then I can come back and verify. Edit: minor note, one additional thing that is in the skill that the tool installs is to direct the agent to create follow up tasks for any bugs or refactor opportunities that it encounters. I find this let's the agent scratch that itch of they see something but instead of getting sidetracked and doing that thing, they create a follow up tasks that I can review later and they can move on. | ||
| ▲ | meisnerd 3 hours ago | parent | prev [-] | |
[dead] | ||