The three features
The project has a defined scope:
- Artist search,
/search/artist?q=name - Discography,
/artist/{id}/albums - Album details,
/album/{id}(tracklist, cover, date)
All endpoints come from the Deezer public API. No authentication is needed for the catalog endpoints used in this project.
---Improve PLAN.md
Review the initial PLAN.md based on AGENTS.md (or CLAUDE.md if I'm using Claude Code). Detail the implementation phases, keep each phase small and testable, add clear acceptance criteria, and only change the initial stack if there is a concrete reason to do so.The agent will improve the draft and organize execution. If it wants to change the initial stack, it should justify that clearly. Don't accept automatically.
---Review and iterate
Read the entire plan and ask yourself:
- Do the phases make sense? Is each one independently testable?
- Is the scope clear? Is any phase too large?
- Is the stack simple enough? Do you understand the suggested technologies?
If something doesn't make sense, iterate:
"This phase is too big, split it in two."
"I don't want that library, suggest something simpler."
"Add acceptance criteria for each phase."
PLAN.md is detailed, saved in the repository, and reviewed by you. Each phase has acceptance criteria you can actually test.
Save your work in Git before moving on. This gives you progress checkpoints, history, and safe rollback points.
git add .
git commit -m "[summarize what changed in this chapter]"
git pushReplace the commit message with a short, real summary of what changed in this chapter.
Chapter 2
0 of 3 checkpointsComplete all checkpoints to unlock the next chapter.
Next up: Build in parts →