gsemet commented on issue #62500: URL: https://github.com/apache/airflow/issues/62500#issuecomment-4310915528
That is the new science of harness engineering ! It is pretty simple to have a mental representation of what is going on: each time you start a session, you bring a contractor on your project that knows nothing of your internal working (actually for an opensource project it does a bit), and you want to give him the minimal information map (the "starter kit" doc) and it will jump to the right section. And you have a "budget" of ~100 rules you can give to your contractor on top of its internal model to adapt to your project, at any given point. That is why splitting task by tech or module is key. That is half the job. The other half is to actually verify the job done (usually you have a coding agent that take a task and code it, and a second subagent that verify it) Yesterday I did a simple change, I changed the place in these task files where the guidelines/rules are place (was after the acceptance criteria, now it is on top), and I get a huge bump in accuracy. That means the tasks needs to be organized correctly for agent to understand. Everybody learns at the same time, that is a bit odd. But it does the job. You can use superpowers or some other SDD framework, even plan mode works fine, but the agents.md priming is key for accuracy (respect of your rules). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
