diff --git a/ChatGPT.md b/ChatGPT.md index 8755f47..452fe38 100644 --- a/ChatGPT.md +++ b/ChatGPT.md @@ -1,5 +1,4 @@ - I actually think that's a stronger choice than trying to reinvent task tracking. The temptation with projects like this is to build everything yourself. Before long you've accidentally decided your first task is "replace GitHub, Jira, Slack, Confluence, and civilization." The scope grows faster than the codebase. Using mature tools where they already excel keeps the interesting work focused on the AI organization itself. @@ -274,8 +273,9 @@ ACT Runner Build, test, validation Markdown Long-lived knowledge and standards That separation is clean. Each tool has one job, and your AI organization becomes the glue that ties them together instead of replacing them. That's a much more maintainable foundation for the kind of long-running, autonomous development studio you're envisioning. - + change it to project manager and we are good. Give me every thing i would need to hand off to claude code, codex, hermes, or even bionic as .md files that i can load into the gitea repo, pull it to my machine and tell the agent to read the files and get to work building. + I can absolutely do that, and I actually think it's the right way to approach this. @@ -430,7 +430,9 @@ And, personally, I think Project Manager is a better title than Chief of Staff. Ad + i dont need it as a single response, i need it as a repository of different files that i can point an agent at and have it sift through and decide what to read and start on. + That's exactly what I was hoping you'd say, because that's a much more ambitious and interesting project.