Background
Read about Scratch Debugems here.
Design Document
Create a brief outline (no more than one page; clear & concise is good) which addresses these topics: your name, name of Debugem, key computing concepts, Scratch concepts, overview, how directions are conveyed to the user including how the user knows how the project should behave, known bugs, difficulties encountered, if I had more time I would...
Debugem Guidelines
It's fine to use Sprites, background images, sounds created by others but the code should be
your own (not a remix).
Focus should be on one or more computing concepts:
conditionals (if, if-else), loops (forever, repeat), nested statements (e.g. loops within loops),
boolean operators (and, or, not), math functions (e.g. square root), broadcasts, variables
Clear instructions
The user should know how end-product should behave (e.g. fix the broken clock, get the
arrow keys to work). Put directions in the Scratch project - e.g. on a background, in the
project notes, or somewhere else where the user will notice them.
Clean code
Well named sprites, variables, broadcasts
No extra code lying around
Comments for tricky parts or hints (right-click in the coding area to add a comment)
If complicated, use the Stage for a "game engine"
No "obfuscated" (intenionally tricky/messy) code
Simple and Effective:
Doesn't take too much time to understand the goal.
Targets key concept(s) well.
Appealling to the target audience - fun for high school or middle school students
Note: silly, crazy is fine as long as it's "appropriate"