Sprint 3 kickoff

Sprint 3 goal: one working JavaScript feature. Not two, not several in progress — one, working, done.

Name your feature first

Before opening the model, fill in this sentence:

"Our feature is ___. A user ___ and the page ___."

Keep it achievable in a single session. "A search bar that filters the resource list as you type" works. "A full map integration" does not. If your feature feels large, ask: what's the smallest version that still feels interactive to a user?

Use CoT for JavaScript

JavaScript breaks in ways HTML and CSS do not. Chain-of-thought prompting produces code that is easier to debug because you can read the plan and catch mistakes before they reach the code.

Format every Sprint 3 prompt with a Plan: section first:

[Feature description]

First write a Plan: section explaining what the function will do step by step —
what it selects, what it responds to, and what it changes.

Then write a Code: section with the complete JavaScript.
Output ONLY the plan and code.

Read the plan before you look at the code. If the plan is wrong, fix it there.

Keep the console open

When something isn't working, open the browser console (right-click anywhere → Inspect → Console tab). It tells you the file, the line, and what went wrong. Keep it open throughout Sprint 3.

Sprint 3 done condition

One JavaScript feature that responds to user input, working in the browser, no console errors.