Comment by jkhdigital
21 days ago
Still basically relies on feeding context through natural language instructions which can be ignored or poorly followed?
The answer is not more natural language guardrails, it is in (progressive) formal specification of workflows and acceptance criteria. The task cannot be marked as complete if it is only accessible through an API that rejects changes lacking proof that acceptance criteria were met.
Some specification exists as formal constraints. Ie: c code will or will not compile.
However some specification only exists in natural language. IE: make this page optimized for a smartphone. The task of turning that vague direction into formal requirements is work in and of itself. The more you can have the llm help with that — the more time it will save you.