Now you can observe up by including the know-how stack you plan to make use of, within the form of a /plan. This lets you change components of your stack, similar to swapping out authentication strategies or storage, permitting you to go from growth to check to deployment. So, you could possibly begin with a primary SQLite implementation for growth by yourself PC, rebuild for MySQL on a take a look at system, after which change to Azure SQL for deployment.
One vital characteristic of Spec Package is that the bottom system prompts are designed to attenuate the danger of hallucinations. If a go can’t implement a perform, it should insert a [NEEDS CLARIFICATION] marker together with a query as a part of the code in order that the agent doesn’t make assumptions and requires particular intent. The bottom prompts embrace checking for this marker, guaranteeing that the system checks itself to keep away from skipping over points which were flagged in earlier passes.
After you have a spec and a plan, you may run the /duties step. This (plus the constraints within the structure) breaks up the venture right into a collection of duties: one for a entrance finish, one for enterprise logic, one for service interfaces, one for configuring and dealing with storage, and so forth. Duties themselves could be made up of subtasks, very similar to the venture planning section of the software program growth life cycle, as you’re employed with venture managers.
