gsd-forensics

<cursor_skill_adapter> ## A. Skill Invocation - This skill is invoked when the user mentions `gsd-forensics` or describes a task matching this skill. - Treat all user text after the skill mention as `{{GSD_ARGS}}`. - If no arguments are present, treat `{{GSD_ARGS}}` as empty. ## B. User Prompting When the workflow needs user input, prompt the user conversationally: - Present options as a numbered list in your response text - Ask the user to reply with their choice - For multi-select, ask for comma-separated numbers ## C. Tool Usage Use these Cursor tools when executing GSD workflows: - `Shell` for running commands (terminal operations) - `StrReplace` for editing existing files - `Read`, `Write`, `Glob`, `Grep`, `Task`, `WebSearch`, `WebFetch`, `TodoWrite` as needed ## D. Subagent Spawning When the workflow needs to spawn a subagent: - Use `Task(subagent_type="generalPurpose", ...)` - The `model` parameter maps to Cursor's model options (e.g., "fast") </cursor_skill_adapter> <objective> Investigate what went wrong during a GSD workflow execution. Analyzes git history, `.planning/` artifacts, and file system state to detect anomalies and generate a structured diagnostic report. Purpose: Diagnose failed or stuck workflows so the user can understand root cause and take corrective action. Output: Forensic report saved to `.planning/forensics/`, presented inline, with optional issue creation. </objective> <execution_context> @/Users/zaneliu/Projects/open-source/friday-ai/.cur...