Define your project specifications

Now we have the perfect environment to build something. But that something is still undefined.

It could be that we've got a great idea in our heads of the content-driven application we'd like to build. But if it's not written down, our LLMs won't know anything about it.

One of the emerging ways to keep projects on track is "spec driven development". Where you create something like a "Product Requirements Document" (PRD) to describe what you're building and how you'd like the LLM to perform tasks. This typically lives at the root of the project as either PRD.md or README.md.

It's not always easy to know everything that you want before you start building anything. So the purpose of this document is not to get everything right in one shot, but to give the LLM a starting point to build.

It may be that you alter this document as your requirements change. Or should your work ever get out of sync with the document, you can prompt the LLM to update the document to match the current state of the project.

If you have a specific project in mind, you could take the example prompts in the rest of the course and modify them to what you are working on. If you don't have an idea of what you'd like to build, then follow the prompts and build with me!

We need to create a PRD that describes the creation of a content-driven web application experience. The content backend will be powered by Sanity. The frontend will be an Astro template. We are trying to build a content model that describes a solar system. We'll start with our own solar system. And our frontend will render facts and images about the solar system.

Given this simplified outline, write a `PRD.md` file to the root of this project. We are in the early planning phases, so only address the requirements as I have discussed.

If you would like to clarify these requirements please ask questions.

Depending on the model that you have chosen, it may write your document, ask clarifying questions, or both. Review the work that it has done and address the questions to the best of your ability.

Remember one of the benefits of AI tooling is the ability to rapidly prototype, so there's nothing that we can't tear down, destroy, and start again.