journey-reportlisted

# Journey Report Generate a structured lifecycle report for a cross-session development journey. ## Variables TARGET: $ARGUMENTS ## Instructions ### 1. Resolve the Journey Journey data is built by reading and chaining distilled sessions. There is no standalone `clens journey` command — journey analysis is done by reading distilled session files directly. 1. List all distilled sessions: `ls .clens/distilled/*.json` (sorted by modification time) 2. Read each distilled JSON to extract: `session_id`, `start_time`, `stats`, `summary`, `user_messages`, `plan_drift` 3. Chain sessions into a journey: - Sessions sharing the same working directory and started within 5 seconds of a `/clear` or compact event belong to the same journey - Order phases chronologically by `start_time` 4. If TARGET is a session ID prefix, find the journey containing that session 5. If TARGET is empty or `--last`, use the most recent journey (by latest session start time) If fewer than 1 distilled session exists, tell the user: > No distilled sessions found. Run `clens distill --last` to distill your sessions first. ### 2. Build the Journey - Load the `session-analysis` skill for schema and interpretation context - For each session in the journey, classify its phase type from the first user prompt: - `/prime` → `prime`, `/brainstorm` → `brainstorm`, `/plan` or `/plan_w_team` → `plan`, `/build` → `build`, `/review` → `review`, `/test` → `test` - "commit" keyword → `commit` - High read:writ