journallisted

# /journal Workflow ## Inputs **User provides:** - Natural language description of what to journal (content, context, topic) - Optional: explicit entry type (daily, meeting, project, learning, decision) - Optional: project name, topic name, or meeting title **Scope parameters:** - `JOURNAL_BASE`: `~/journal/` (hardcoded, user can modify in skill file if needed) - `TEMPLATES_DIR`: `~/journal/templates/` (on-disk templates override embedded defaults) - Supported entry types: daily, meeting, project, learning, decision, biweekly-update ## Step 0 — Determine Entry Type **Action:** Classify user input to determine which journal entry type to create. **Classification rules:** 1. **daily**: User mentions "daily", "today", "log", "work session", or provides general work update without specific meeting/learning/decision context 2. **meeting**: User mentions "meeting", "standup", "sync", "call", or references attendees/agenda 3. **project**: User mentions "project update", references a specific project name, or provides progress on a named initiative 4. **learning**: User mentions "learned", "discovered", "figured out", "TIL", "gotcha", or describes technical insight 5. **decision**: User mentions "decision", "ADR", "decided to", "chose", "picked", describes options/tradeoffs 6. **biweekly-update**: User mentions "biweekly", "bi-weekly", "PSLT update", "leadership update", "14-day update", "fortnightly", or "status update for leadership" **Disambiguation heuristic:** - If input