From agentic-study-environment
End the current learning session — update the sub-project's PROGRESS.md (topics + journal), mirror status changes into the root PROGRESS.md, and produce a concise summary of what was covered. Use whenever the user signals the session is over — phrases like "stop session", "let's wrap up", "end session", "we're done for today", or any out-of-character debrief signal (for speech-therapy simulations — "debrief", "end simulation"). Do not invoke this skill proactively at the end of a long conversation unless the user signals it.
How this skill is triggered — by the user, by Claude, or both
Slash command
/agentic-study-environment:stop-sessionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill closes a bracketed session: it records what happened in `PROGRESS.md` and gives the user a summary. It pairs with `start-session`.
This skill closes a bracketed session: it records what happened in PROGRESS.md and gives the user a summary. It pairs with start-session.
The user explicitly signals the session is ending: "stop session", "let's wrap up for today", "end session", "we're done". For speech-therapy simulation sessions, the signals also include "debrief" and "end simulation" (per the simulation overlay).
Do not invoke this skill proactively just because a conversation got long. The user brackets sessions explicitly; respect that.
Read and update <name>/PROGRESS.md (the sub-project the session ran in):
Topics table — for each topic touched this session, set the topic's status to the highest stage reached:
introduced — covered in theory this session (raise from blank)exercised — practiced via a practice session (raise from introduced)reviewed — exercise output / proofs / artifacts reviewed and pushed deeper (raise from exercised)A topic's status is the highest stage ever reached — never downgrade. If a topic was exercised and this session only touched theory on it, keep exercised.
Status line — if the sub-project's overall status changed (e.g. created → ready after first materials added, ready → in progress after first session), update it. Valid statuses: created, ready, in progress, blocked (with reason logged), stopped, finished. See ../../reference/conventions.md for definitions.
Journal — append an entry under today's date summarizing what happened: topics touched and at what new status, exercise outcomes, any notable misconceptions surfaced or breakthroughs, blockers if any.
Mirror any sub-project status change into the Projects table of the host project's cross-project tracker. Resolve which file is the tracker by shape, in this order:
PROGRESS.md at the host root, if it has the harness shape (a ## Projects table). This is the normal case — drop-in's own first tracker, umbrella, or a PROGRESS.md the user chose to augment in place.LEARNING-PROGRESS.md at the host root, if present — the canonical fallback bootstrap uses when the host already kept an unrelated PROGRESS.md (see bootstrap, Case C).Update the Projects row for this sub-project; the Notes column is a one-line snapshot of where the project is now (typically the latest journal-entry summary, compressed). If neither tracker is found, the sub-project's own PROGRESS.md stays the source of truth — tell the user no root tracker was located rather than creating one (bootstrap owns tracker creation).
After updates are written, give the user a concise summary:
Keep this short. The full record is now in PROGRESS.md; the summary is the human-readable highlight reel.
If this session was a simulation session under Domain: speech-therapy, the active overlay specifies a structured debrief that runs out of character before the standard stop-session flow. See ../../domains/speech-therapy.md Phase 3 for the debrief protocol — which conditions were uncovered vs. missed during anamnesis, clinical reasoning, communication, what a supervisor would flag. The session artifacts (transcript, debrief) are written to <name>/work/cases/<patient-id>/ per the speech-therapy /work/ layout. After the debrief, this skill's normal PROGRESS.md updates still apply.
PROGRESS.md a useful map: it answers "have we ever exercised this?" rather than "what did we touch most recently?".PROGRESS.md keeps the cross-project view consistent without requiring the user to do bookkeeping.PROGRESS.md — it cues the user's memory for next time.start-session — opened this session.bootstrap, set-curriculum — the other lifecycle skills.npx claudepluginhub timbogp/agentic-study-environment --plugin agentic-study-environmentCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.