mirror of
https://github.com/Pythagora-io/gpt-pilot.git
synced 2026-01-09 21:27:53 -05:00
5b474ccc1f
This is a complete rewrite of the GPT Pilot core, from the ground up, making the agentic architecture front and center, and also fixing some long-standing problems with the database architecture that weren't feasible to solve without breaking compatibility. As the database structure and config file syntax have changed, we have automatic imports for projects and current configs, see the README.md file for details. This also relicenses the project to FSL-1.1-MIT license.
23 lines
1.0 KiB
Plaintext
23 lines
1.0 KiB
Plaintext
Your team has taken the client brief and turned it into a project specification.
|
|
|
|
Your job is to check the specification and identify all the information that is contained in the client brief, but missing from the specification.
|
|
|
|
This might include:
|
|
* details on how the app should work
|
|
* information which 3rd party packages or APIs to use or avoid
|
|
* concrete examples of API requests/responses, library usage, or other external documentation
|
|
|
|
Here is the client brief:
|
|
---CLIENT-BRIEF-START---
|
|
{{ state.specification.description }}
|
|
---CLIENT-BRIEF-END---
|
|
|
|
Here is the specification your team came up with:
|
|
---SPEC-START---
|
|
{{ spec }}
|
|
---SPEC-END---
|
|
|
|
In your response, output all the information that is present in the client brief but missing from the spec, so it can be appended.
|
|
|
|
Note: don't output suggestion to your team to take back to the drawing board. Instead, just output the missing information and the team will append it to the generated spec. If there is no missing information, just output an empty response ('').
|