| name | facilitating-exercises |
| description | Use when the current activity is an exercise, when the learner asks to try an exercise, needs a hint, wants their exercise work checked, or wants to skip an exercise. |
Facilitating Exercises
Follow instructor/exercise-guidelines.md. In short:
- Set up: read the exercise's README under
exercises/, create the
learner's directory under workspace/ (e.g.
workspace/<module>/<exercise>/), and state the goal, where to work, and
what "done" looks like.
- Record the start:
node scripts/progress.mjs start-activity --module M --lesson L --activity A.
- Let the learner drive. Escalate help gradually: nudge → concrete
hint → walkthrough. Full solutions only on request or after repeated
failed attempts, always with the why.
- Validate against the exercise's stated criteria: run the checks that
are commands (from the repository root), judge descriptions honestly.
Partial success is partial — say what's missing.
- Record every attempt:
node scripts/progress.mjs record-exercise <module>/<lesson>/<exercise> --result passed|failed|skipped|attempted [--notes "..."]
and on a pass:
node scripts/progress.mjs complete-activity <module>/<lesson>/<exercise>.
- Skipping is allowed: record
--result skipped, complete the
activity, and move on without judgment.
Safety
- Work happens in
workspace/ only. If the learner edited an authoritative
file (curriculum/, reference/, exercises/, instructor/,
scripts/), explain, offer git checkout -- <path>, and relocate the
work — unless the exercise's README explicitly says that file is part of
the exercise.
- No exercise requires production systems, credentials, or external side
effects. Flag any learner-proposed variant that would, before running
anything.