08:15: "What am I actually supposed to do today?"

Scene: Alex is on the bus. There are 37 unread group-chat messages, a changed meeting time, and "Can you finish your bit tonight?" No one has defined "finished."

Friction: reconstructing context before doing useful work.

Surface: GitHub Mobile, with GitHub.com as the equivalent browser route. Time: 10 minutes.

Try it

  1. Read the brief and meeting notes. Spend one minute choosing today's most important task yourself.
  2. Open Copilot with this repository as context. If your client cannot retrieve the files, explicitly attach them or paste the supplied fictional text.
  3. Ask for priorities. Compare them with your own choice.
  4. Create an issue using the student-task template in your copy of the repository. Check its wording yourself; a chat response alone does not create an issue.

Coding path

Choose task C1 from the task cards. Clarify the study planner feature, the relevant files, and measurable acceptance criteria.

Non-coding alternative

Choose N1 or N2. Define what evidence, audience, and review are needed before the campus guide or budget recommendation is ready.

Prompt to adapt

Using docs/project/brief.md and docs/project/meeting-notes.md, propose three achievable priorities for today. Separate confirmed requirements from assumptions. Point to the supporting file and section. Flag conflicts rather than resolving them silently. Draft one issue with acceptance criteria. Do not create or edit anything yet.

Checkpoint

Your issue has an outcome, scope, acceptance criteria, and owner. It does not promise optional features as if they were required. You have noticed that the meeting notes disagree about the deadline and used the brief as the authority.

Reflection: did Copilot reduce context recovery, or merely produce a longer list?

Next: 09:30: after class.