Now you can observe up by including the expertise stack you plan to make use of, within the form of a /plan. This lets you change components of your stack, equivalent to swapping out authentication strategies or storage, permitting you to go from growth to check to deployment. So, you possibly can 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 essential function of Spec Equipment is that the bottom system prompts are designed to attenuate the chance of hallucinations. If a cross can’t implement a operate, it’ll 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, making certain 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’ll be able to run the /duties step. This (plus the constraints within the structure) breaks up the undertaking 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 might be made up of subtasks, very like the undertaking planning section of the software program growth life cycle, as you’re employed with undertaking managers.
