shepherd-startlisted

# /shepherd-start {TICKET-ID} — Bug Investigation Session Begin a focused investigation session for a single bug. This command sets up context, loads institutional memory, and prepares a structured investigation plan. **Audience:** PMs, designers, or developers. No code knowledge required for investigation; code knowledge only needed if you plan to fix it yourself. ## Arguments - `{TICKET-ID}` (required): The bug tracker ID (e.g., PROJ-1234, #456) ## Workflow ### 1. Load Configuration Read `.claude/triage.config.yaml` for project settings. ### 2. Pre-Flight Checks - If `team.git_email` is set, verify: `git config user.email` matches. If not, warn: ``` "Git email mismatch. Expected: {git_email}, Got: {actual}." "Fix: git config user.email {git_email}" ``` - Verify clean working directory: `git status --porcelain`. If dirty: ``` "Working directory has uncommitted changes. Commit or stash before starting a new session." ``` - Check that we're on main/master branch. If not, warn. ### 3. Auto-Sync Backlog If `.claude/backlog-live.md` doesn't exist or is older than 24 hours, run `/shepherd-sync` first. ### 4. Pull Full Bug Details Load the appropriate adapter and fetch complete bug details: **For Jira:** - Title, description, priority, status, assignee, reporter - All comments (chronological) - Attachments and screenshots - Linked issues - Sprint history **For Linear:** - Title, description, priority, status, assignee - Comments and activity - Related i