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 parts of your stack, akin to swapping out authentication strategies or storage, permitting you to go from improvement to check to deployment. So, you might begin with a primary SQLite implementation for improvement by yourself PC, rebuild for MySQL on a take a look at system, after which change to Azure SQL for deployment.
One vital function of Spec Package is that the bottom system prompts are designed to reduce the chance of hallucinations. If a cross can’t implement a operate, 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 have been flagged in earlier passes.
After getting a spec and a plan, you possibly can run the /duties step. This (plus the constraints within the structure) breaks up the challenge right into a sequence 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 like the challenge planning section of the software program improvement life cycle, as you’re employed with challenge managers.
