Should you harness the harness: so, should you?

Description and use

<p>Four parts of machinery. This one is the decision.</p> <p>It is a yes or no. Either the agent runs your procedure, or your procedure runs the agent. Neither side is only one thing: an orchestrator skill is just the pattern the previous series happened to use, and on the other side a <code>Makefile</code> that calls the coding agent at each step is already harnessing the harness. Nobody sells that one, and it works.</p> <p>This part names no winner. Tools change every few months. Where a procedure should live does not.</p> <p><em>Assumes parts one and two. Three and four are a worked example

Problem

<p>Four parts of machinery. This one is the decision.</p> <p>It is a yes or no. Either the agent runs your procedure, or your procedure runs the agent. Neither side is only one thing: an orchestrator skill is just the pattern the previous series happened to use, and on the other side a <code>Makefile</code> that calls the coding agent at each step is already harnessing the harness. Nobody sells that one, and it works.</p> <p>This part names no winner. Tools change every few months. Where a procedure should live does not.</p> <p><em>Assumes parts one and two. Three and four are a worked example

Outcome

<p>Four parts of machinery. This one is the decision.</p> <p>It is a yes or no. Either the agent runs your procedure, or your procedure runs the agent. Neither side is only one thing: an orchestrator skill is just the pattern the previous series happened to use, and on the other side a <code>Makefile</code> that calls the coding agent at each step is already harnessing the harness. Nobody sells that one, and it works.</p> <p>This part names no winner. Tools change every few months. Where a procedure should live does not.</p> <p><em>Assumes parts one and two. Three and four are a worked example

Evidence

Should you harness the harness: so, should you?

Source