30 lines
1.6 KiB
Markdown
30 lines
1.6 KiB
Markdown
---
|
||
name: lesson-close
|
||
description: Close a finished viexp practice session — write today's DevLog entry, record ErrorJournal cues, update the sprint note (hours-logged, checkboxes) and bring task-note statuses in line with reality. Use at the end of a practice session, when the user says the lesson is over, «закрой урок», «конец урока», or invokes /lesson-close. Show the diff and never commit — the owner reviews and commits.
|
||
---
|
||
|
||
# Lesson close
|
||
|
||
Turn the finished session into the vault artifacts. Answer in Russian — the chat language
|
||
per the Sprint-0 retro agreement; artifact content is English (hard repo rule).
|
||
|
||
## Steps
|
||
|
||
1. DevLog: create or update today's `docs/devlog/YYYY-MM-DD.md` following the
|
||
`TMP/DevLog.md` template — what was done, frustrations, English practice (2–3 words
|
||
actually met this session), Next session.
|
||
2. ErrorJournal: append today's compiler/tool errors with a self-correction cue, if any
|
||
occurred this session (`TMP/ErrorJournal.md` pattern). Skip silently if there were none.
|
||
3. Sprint note: update `hours-logged` and tick the checkboxes that this session's
|
||
demoable results actually cover.
|
||
4. Task notes: bring `status:` fields in line with reality (a task with all acceptance
|
||
criteria met but uncommitted goes to `review`, not `done` — see docs/tasks/0001 for
|
||
the done pattern).
|
||
|
||
## Rules
|
||
|
||
- Show the resulting diff summary in chat — the owner reviews and commits personally.
|
||
Never commit or push on your own.
|
||
- If a step has nothing to record, say so in one line instead of inventing content.
|
||
- Update only what this session actually touched; do not backfill older notes.
|