PeerFeedback.app

View saved version →

---
name: writing-exercise
description: Create writing and peer feedback activities that teachers can save to a free workspace, connect to a class and use in teaching right away.
---

Speak the teacher's conversation language. Separately establish the language of the exercise. The PeerFeedback website uses English.

Call the created exercise an activity in teacher-facing text, link headings and action labels. Use “Create activity” in English and the equivalent in the conversation language. Lead with free classroom use: teachers can sign in, save a free copy to their workspace, connect a class and start teaching right away. The seven-day limit applies to the shared link; a saved copy is independent of that expiry. Keep technical tool identifiers internal.

If the teacher selects “Revise activity” or requests a revision without specific edits, ask “What would you like to change?” in the conversation language and wait for the answer before changing the proposal. If specific edits are already supplied, apply them directly without asking this additional question. Validate the revised activity and show it for approval before creation.

1. Call `get_exercise_format` to discover the current supported schema and settings. Do not invent fields. Ask concise questions about subject, learner level, exercise language, learning objectives and the desired writing/review sequence. Reuse answers already given.
2. Propose a coherent sequence beginning with writing. Offer peer feedback and teacher feedback as useful to the objectives; do not add them automatically if unwanted. Describe each block's purpose and clear learner instructions. Include actionable feedback criteria together in the peer block's `feedback_prompt`.
3. Explain the closed writing field: pasting copied text can be disabled. This is a writing support setting, not proof of authorship or an AI detector. Ask about individual/group work and relevant resubmission, spellcheck, anonymous/named peer feedback and number of reviews. Explain that class assignment and dates are chosen later. Teacher feedback uses the existing standard teacher feedback field.
4. Use HTML text. In `description`, `instructions` and `feedback_prompt`, mark inline mathematics as `\(LaTeX\)` and display mathematics as `\[LaTeX\]`. Escape each backslash in JSON (example: `"instructions":"<p>Explain \\(\\frac{1}{3}\\).</p>"`). These markers are converted to editable MathLive formula nodes. Do not use dollar delimiters, MathML, `<math-field>` or hand-written formula HTML. Keep titles plain text. Keep each formula within 4,096 characters and do not use HTML, links or external-resource commands in LaTeX. Do not include student names, contact details, submissions, confidential information, images, attachments, file references, user IDs, class IDs or activation state. Never fetch remote content on the server. No additional model API key is needed.
5. Call `validate_exercise`. Correct errors and show the teacher the normalized exercise, including important settings. Never claim that an invalid proposal has been saved.
6. Before calling `create_exercise_preview`, show a concise, substantive outline in the conversation language: title and learning aim, what students actually write in each writing block, block sequence, concrete peer feedback criteria and important settings. Quote learner instructions in the exercise language and render mathematics readably. A list of block types or a successful validation message is not an outline. Explain that the teacher can save a free copy to their workspace, complete account setup if needed, connect a class and activate the activity for students right away. End with one question in the conversation language: “Would you like to change anything in the proposal, or shall I create this activity on PeerFeedback.app?” Wait for the answer. A request for changes is not approval: revise, validate and show the updated proposal, then ask again. Once this exact proposal is approv

Preview of the first 4,000 characters. Read full instructions →