AI Feedback Prompts

Use AI as a rubric-aware reviewer — not as a code generator.

Purpose

These prompts are designed to help you get constructive feedback and verify that your Create PT meets requirements, without generating or rewriting your code.

Rule: AI may help you check requirements and clarity. AI may not write, refactor, or redesign your solution.

Required Rules (Paste This Into Every Prompt)

Copy/paste this block at the top of any prompt you use. This keeps the feedback ethical and keeps you as the author of your work.

1
Rules for this review:
2
- Do NOT rewrite, refactor, or generate code.
3
- Do NOT suggest specific lines of code to add/change.
4
- Only identify whether Create PT requirements are met and explain why or why not.
5
- If something is missing, describe the conceptual gap, not how to implement it.

Approved Prompt Library

1) Full Create PT Compliance Review

Best for: “Am I meeting the requirements?” Use near the middle/end of your build.

I am completing the AP CSP Create Performance Task.

Below is my program code.

Your job is to act as a rubric reviewer, not a programmer.

Rules for this review:
- Do NOT rewrite, refactor, or generate code.
- Do NOT suggest specific lines of code to add/change.
- Only identify whether Create PT requirements are met and explain why or why not.
- If something is missing, describe the conceptual gap, not how to implement it.


Check the following:
1. Is there real user input?
2. Is there a list that manages program state meaningfully?
3. Is there a student-developed procedure with at least one parameter?
4. Does that procedure contain sequencing, selection, and iteration?
5. Is output clearly produced based on input and processing?

Respond in a checklist format with brief explanations.

[PASTE MY CODE BELOW]

2) Procedure + Algorithm Verification (Most Common Failure Point)

Best for: checking the function requirement without changing any code.

Review ONLY the student-developed procedure in the code below.

Rules for this review:
- Do NOT rewrite, refactor, or generate code.
- Do NOT suggest specific lines of code to add/change.
- Only identify whether Create PT requirements are met and explain why or why not.
- If something is missing, describe the conceptual gap, not how to implement it.


Answer these questions:
1. Does the procedure have at least one parameter?
2. Is the procedure actually called somewhere in the program?
3. Does the procedure execute multiple steps top-to-bottom? (sequencing)
4. Does it contain a conditional decision? (selection)
5. Does it contain a loop? (iteration)
6. Are all of these inside the same procedure?

Explain your reasoning in plain English.

[PASTE MY PROCEDURE + THE CALL SITE BELOW]

3) “Sequencing” Without AP Vocabulary

Best for: avoiding the “sequencing” mental trap.

Look at the procedure below.

Rules for this review:
- Do NOT rewrite, refactor, or generate code.
- Do NOT suggest specific lines of code to add/change.
- Only identify whether Create PT requirements are met and explain why or why not.
- If something is missing, describe the conceptual gap, not how to implement it.


Question:
Does this procedure execute multiple steps in a clear top-to-bottom order before producing a result?

Explain your answer WITHOUT using AP terminology.

[PASTE MY PROCEDURE BELOW]

4) List Use / Managing Complexity Check

Best for: proving your list is meaningful, not decorative.

Review how the list is used in the program below.

Rules for this review:
- Do NOT rewrite, refactor, or generate code.
- Do NOT suggest specific lines of code to add/change.
- Only identify whether Create PT requirements are met and explain why or why not.
- If something is missing, describe the conceptual gap, not how to implement it.


Answer:
1. What information does the list store?
2. How is the list used more than once?
3. Would the program be harder to write or explain without this list?

If the list does NOT manage complexity, explain why in conceptual terms only.

[PASTE MY CODE BELOW]

5) Video Readiness Audit (Input → Output Evidence)

Best for: scripting a clean Create PT video without changing your program.

Assume you are a grader watching a Create PT video.

Based on the program below, answer:
1. What input should be shown in the video?
2. What processing should be visible?
3. What output must be clearly shown?

Rules for this review:
- Do NOT rewrite, refactor, or generate code.
- Do NOT suggest specific lines of code to add/change.
- Only identify whether Create PT requirements are met and explain why or why not.
- If something is missing, describe the conceptual gap, not how to implement it.


Only describe what must be demonstrated in the video.

[PASTE MY CODE BELOW]

6) Written Response Self-Check (No Rewriting)

Best for: checking whether your writing is complete and rubric-aligned.

Below is my Create PT written response draft.

Rules for this review:
- Do NOT rewrite, refactor, or generate code.
- Do NOT suggest specific lines of code to add/change.
- Only identify whether Create PT requirements are met and explain why or why not.
- If something is missing, describe the conceptual gap, not how to implement it.


Check:
1. Do I clearly identify my list?
2. Do I explain what my procedure does?
3. Do I explain how the algorithm works?
4. Do I explain how input affects output?

Respond with:
- Missing
- Weak
- Clear

Include a brief explanation for each.

[PASTE MY WRITTEN RESPONSE BELOW]

Student Tips (Keep It Ethical)

Ask for yes/no checks and conceptual gaps — not solutions.
If AI starts writing code anyway, stop and re-run your prompt with the required rules.
You should be able to explain every line in your program without AI.

Best mindset: treat AI like a code reviewer that can only comment — it cannot commit changes.

Reminder

Your Create PT must be your own work. Use these prompts to check and clarify, not to generate solutions.