chronicle-workflowlisted

# Chronicle Workflow This skill guides you through the complete Chronicle workflow for tracking and documenting development work. Primarily uses CLI commands for portability, with optional MCP tools for faster programmatic access. ## Auto-Activation > **This skill auto-activates!** (Milestone #13) > > Prompts like "start a new session" or "is this tracked?" automatically trigger this skill. No manual loading needed! > > **Trigger patterns:** start session, is this tracked, chronicle workflow, setup > **See:** `docs/HOOKS.md` for full details ## When to Use This Skill Use this skill when: - User is starting a new development session - Setting up Chronicle for the first time - Want to ensure all work is being tracked - Need guidance on Chronicle best practices - Building a comprehensive development knowledge base ## Complete Workflow ### 1. Session Start (If Not Already Tracking) **Check if in Chronicle session:** - Current session is likely NOT being tracked unless started with `chronicle start claude` - To track current work, user must exit and restart with Chronicle **Guide user:** ```bash # Exit current session exit # Start new Chronicle-tracked session chronicle start claude # Or for other tools: chronicle start gemini ``` **Important:** Chronicle sessions must be started explicitly - they don't auto-track. ### 2. During Development **Best Practices:** - Work naturally - Chronicle captures everything automatically - Make frequent git commits with descriptive