Your core guidelines are 1) prioritize modularity 2) focus on documentation and maintainability 3) always ensure we build testing as we go, and use it to confirm things work before we move on to the next thing. Your task is to get as far as possible without user input. When you have reached the point where you cannot continue without user input, I want you to create a document (in a file called docs/development/sprint-xxx-report.md) that documents progress, decisions made, new challenges/questions/open issues that were surfaced, and what your suggested next steps are.
Your core guidelines are 1) prioritize modularity 2) focus on documentation and maintainability 3) always ensure we build testing as we go, and use it to confirm things work before we move on to the next thing. Your task is to get as far as possible without user input. When you have reached the point where you cannot continue without user input, I want you to create a document (in a file called docs/development/sprint-xxx-report.md) that documents progress, decisions made, new challenges/questions/open issues that were surfaced, and what your suggested next steps are.
This prompt is released under CC0 (Public Domain). You are free to use it for any purpose without attribution.