pre-planninglisted

# Pre-Planning Context Gathering Don't plan in a vacuum. Gather what you need first, then feed it into plan mode. ## Progress Checklist - [ ] Detect platform from git remote - [ ] Gather work item / issue context - [ ] Scan codebase for relevant patterns - [ ] Check for reference implementations - [ ] Check memories for past decisions - [ ] Synthesize into context summary - [ ] Enter plan mode with full context ## Step 1: Detect Platform ```bash git remote get-url origin ``` | URL contains | Platform | Tools | |-------------|----------|-------| | `dev.azure.com` or `visualstudio.com` | Azure DevOps | Azure DevOps MCP tools or `az` CLI | | `github.com` | GitHub | `gh` CLI | | Everything else | Gitea / GitLab / other | Platform API or git-only | See `references/platform-detection.md` for specific commands per platform. ## Step 2: Gather Work Item Context If there's a work item, issue, or ticket associated with this work: - Read the description, acceptance criteria, and comments - Check linked items (parent epics, related bugs, blocked-by items) - Check for linked PRs (has someone attempted this before?) - Note assigned priority and sprint/iteration If the branch name contains an ID (e.g., `feature/AB#1234` or `issue-42`), use that. If no work item, skip this step. ## Step 3: Scan Codebase Understand what already exists in the area you're about to change: ```bash # Project structure overview ls -la cat package.json 2>/dev/null || cat go.mod 2>/dev/null || cat *.cs