Planning Template (LLM + Submission)

1) LLM Prompt Starter (Technical Purpose)

Use this to get precise, technical help from an LLM. Fill the brackets.

Goal:
I need to build [what] for [who/users] that does [core outcome].

Constraints:
- Must run in [browser/version or environment]
- Allowed tools: [HTML/CSS/JS only?]
- Must include: [2 interactions, reset button, etc.]
- Avoid: [libraries, images, audio, etc.]

Inputs / Outputs:
Inputs: [buttons, sliders, text fields]
Outputs: [numbers, graphs, status text, visuals]

Data / Content:
[Any facts, topic focus, required labels]

Deliverable:
Give me [file list], with [index.html + style.css + script.js],
and explain how to customize it.
    

2) Example Prompt

Goal:
Build an interactive webpage that explains carbon footprints for middle schoolers.

Constraints:
- HTML/CSS/JS only
- 2 interactions minimum
- Reset button required
- No external libraries

Inputs / Outputs:
Inputs: slider for miles driven, dropdown for vehicle type
Outputs: total CO2 estimate, color-coded impact level

Deliverable:
Give me index.html, style.css, script.js with simple instructions.
    

3) Submission Guide (Quick)

• Folder name: Period#-FirstName-ID
• Required folders: info/ and games/
• Each project folder must include index.html
• Keep names simple (letters/numbers/hyphens)

4) README & CHANGELOG (Iterative / Agentic)

README (what + how)

Project: [Title]
Purpose: [What it teaches or shows]
How to Use:
1) [Step 1]
2) [Step 2]
Inputs: [List]
Outputs: [List]
    

CHANGELOG (what changed)

v1.0 - Initial build
- Added [feature]
- Added [interaction]

v1.1 - Improvements
- Fixed [bug]
- Improved [UI/UX]
    

Use the README to explain the project and the CHANGELOG to track updates. This helps agents (and teachers) understand changes over time.