This prompt describes a systematic approach to planning and executing a project through iterative development.
Initial Blueprint Creation: Start by drafting a comprehensive, detailed plan outlining the entire scope of the project. This blueprint serves as an overarching guide for what needs to be accomplished.
Chunking into Iterative Segments: Once you have a solid plan, divide the project into smaller segments or chunks. Each chunk should build upon previous ones, allowing gradual progression toward the final goal.
Further Breakdown of Chunks: Take each segment and break it down further into more manageable steps. This involves deconstructing each chunk to ensure all necessary tasks are identified and can be executed efficiently.
Review for Balance: Evaluate these smaller steps to ensure they strike a balance between being small enough for safe implementation with strong testing, yet large enough to contribute meaningfully to the project's progress.
Iterative Refinement: Continuously review and refine these steps. Iterate through this process until you are satisfied that each step is appropriately sized for effective development without introducing unnecessary risk or delay.
Focus on Safe Implementation: Emphasize safety in execution by ensuring thorough testing at every stage, reducing the likelihood of errors as the project advances.
Adaptability and Responsiveness: The iterative nature of this approach allows for adjustments based on feedback and new insights during each cycle, making it adaptable to changes or unforeseen challenges.
This method aims to create a well-organized, risk-mitigated path forward, ensuring that progress is both steady and secure throughout the project's lifecycle.
Draft a detailed, step-by-step blueprint for building this project. Then, once you have a solid plan, break it down into small, iterative chunks that build on each other. Look at these chunks and then go another round to break it into small steps. Review the results and make sure that the steps are small enough to be implemented safely with strong testing, but big enough to move the project forward. Iterate until you feel that the steps are right sized for this project.
From here you should have the foundation to provide a series of prompts for a code-generation LLM that will implement each step in a test-driven manner. Prioritize best practices, incremental progress, and early testing, ensuring no big jumps in complexity at any stage. Make sure that each prompt builds on the previous prompts, and ends with wiring things together. There should be no hanging or orphaned code that isn't integrated into a previous step.
Make sure and separate each prompt section. Use markdown with a checkbox for each step. Each prompt should be tagged as text using code tags. The goal is to output prompts, but context, etc is important as well.
<SPEC>
{{Development Spec}}
</SPEC>