retrospect

# retrospect Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md). create and run a retrospect process: ### Run Selection - `--all` or "all runs": list all completed/failed runs and analyze collectively - Multiple run IDs: analyze each specified run - Single run ID or no ID: existing behavior (latest run) - In interactive mode with no run specified: ask user whether to analyze latest, select specific runs, or all runs ### Cross-Run Analysis (multi-run mode) When analyzing multiple runs, the retrospect process should additionally cover: - Common failure patterns across runs - Velocity trends (tasks/time across runs) - Process evolution (how processes changed) - Repeated breakpoint patterns - Aggregate quality metrics implementations notes (for the process): - The process should analyze the run, the process that was followed, and provide suggestions for improvements, optimizations, and fixes. - The process should such have many breakpoints where the user can steer the process, provide feedback, and make decisions about how to proceed with the retrospect. - The process should be designed to be flexible and adaptable to different types of runs, projects, and goals, and should be able to provide insights and suggestions that are relevant and actionable for the user. (modification to the process, skills, etc.) - The process should be designed to be iterative, allowing the user to go through multiple rounds of analysis and improvem...