kb-day-start
Use this skill when the user starts a new work day or asks for a morning brief.
Steps
- •Anchor time:
bash
date '+%Y-%m-%d %H:%M (%A) %Z'
- •Refresh the brief from Jira (best-effort):
bash
.venv/bin/python scripts/kb.py day-start
- •If Jira auth is missing/unavailable: tell the user to create/update
.envwithJIRA_URL+JIRA_TOKEN(and optionallyJIRA_USERNAME). Continue by reading the existingnotes/work/daily-brief.md/ latest snapshot if present.
- •Read and summarize
notes/work/daily-brief.md:
- •Overdue / due soon (if present)
- •High priority / In progress / Review first; then “Сделать/Backlog”
- •“Needs Review” items
- •Reminders surfaced by the brief (if present)
In every task line, include title next to key (avoid bare IDs).
- •Ensure today’s end-of-day container exists:
- •
day-startalready callsopen-day, but ifnotes/work/end-of-day.mdis missing or has the wrong date, run:
bash
.venv/bin/python scripts/kb.py open-day
- •Ask clarifying questions only if needed:
- •Confirm top‑3 priorities for today.
- •If “Needs Review” has items: ask to confirm theme mapping / intent.
- •If tasks look stale or missing: ask whether the Jira JQL in
configs/kb.tomlneeds changes.
Output expectations
- •Keep the response short (about 1 screen).
- •Do not manually edit
notes/work/daily-brief.md. - •Do not invent statuses, time spent, or outcomes.