Files
viexp/.agents/skills/lesson-plan/SKILL.md
T

2.4 KiB
Raw Blame History

name, description
name description
lesson-plan Build today's viexp practice-session plan from the vault itself (active sprint note, latest DevLog "Next session", open tasks and milestone issues). Use at the start of any practice session in this repo — when the user asks for a lesson plan, «план урока», «план на сегодня», or invokes /lesson-plan. Produce the plan only and never start the work before an explicit go-ahead.

Lesson plan

Assemble today's lesson plan so the owner does not spend session time planning or drift from the methodology (sprint rhythm 5/30/10, one drill = one commit). Answer in Russian — the chat language per the Sprint-0 retro agreement; keep the section headers exactly as given below.

Gather the context yourself

  1. Active sprint: the note in docs/sprints/ with status: active in frontmatter.
  2. The latest docs/devlog/*.md by date — its «Next session» section.
  3. Open tasks of that sprint: docs/tasks/ notes with status: todo | in-progress | blocked.
  4. Open issues of the sprint's milestone via tea (see docs/workflows/gitea-workflow.md for the quirks; scripts/gitea-issues.sh maps label names to IDs). If tea fails or is slow, fall back to the task notes and say so.

Answer strictly in this format

Где мы — 2–3 строки: последний коммит, что осталось с прошлого урока.
Цель урока — одна фраза + номер task/issue.
Дрели — 2–4 шт. по 20–30 мин, каждая: название / что делаю /
  критерий готовности (демонстрируемый результат). Размер дрели = один коммит.
Финал — последние 10 минут: DevLog, ErrorJournal, синхронизировать доску.
Бюджет урока: __ мин — сумма дрелей плюс финал не превышает бюджет.

If the user passed a number with the command (e.g. /lesson-plan 45), use it as the budget; otherwise leave __ мин for the owner to fill.

Rules

  • If the drills do not fit the budget, cut the number of drills — never shorten a drill below 20 minutes.
  • If something is missing or unclear, pick an obvious default, mark it «допущение», and move on — do not ask questions.
  • Until the owner replies «поехали» (or corrects a point), do nothing: no file edits, no commits, no issue changes.