issue-analyzerlisted

# Issue Analyzer ## Purpose Analyzes a GitHub issue and decomposes it into atomic implementation tasks that can be dispatched to `task-implementer` sub-agents. Designed to run autonomously as a sub-agent — no user interaction required. **Input:** GitHub issue URL (or repo + number) + codebase path(s) **Output:** JSON analysis object with one task entry per atomic task, each containing full context for implementation ## When to Use - Orchestrator needs to break an issue into implementable tasks - Planning AI-driven implementation of a GitHub issue - Understanding scope and affected areas before coding ## Architecture: 4 Phases ``` Phase 1: COLLECT → Fetch all issue data from GitHub Phase 2: ANALYZE → Extract intent, find affected code areas Phase 3: DECOMPOSE → Break into atomic tasks with dependencies Phase 4: FORMALIZE → Emit structured JSON analysis object ``` --- ## Workflow ``` Issue Analyzer Progress: - [ ] Phase 1: Collect issue data from GitHub - [ ] Phase 2: Analyze intent and search codebase - [ ] Phase 3: Decompose into atomic tasks - [ ] Phase 4: Formalize as JSON output ``` ### Phase 1: COLLECT Fetch all available data about the issue using `gh` CLI. **1.1 Core issue data:** ```bash gh issue view <NUMBER> --repo <OWNER/REPO> --json title,body,state,labels,assignees,milestone,comments,projectItems ``` **1.2 Timeline events (cross-references, linked PRs, assignments):** ```bash gh api repos/<OWNER>/<REPO>/issues/<NUMBER>/timeline --paginate ```