technical-analysislisted

# Technical Analysis Skill Analyze the user's feature request and produce a structured technical analysis document with method-level details, notes, and estimation. ## When to use - `/technical-analysis` - User says "technical analysis", "estimation", or "breakdown". - User provides a task link (Phabricator, Jira, GitHub issue) and asks for planning or analysis. - User asks "how long would this take", "what would need to change", or "where do I start". - User asks for an architecture review or refactoring candidates ("find deepening opportunities"). ## Format Produce output in this exact structure: ``` ### Technical Analysis: 1. <Subtask title and changes grouped by logical change>: - `<method_name>` at `<relative_file_path>` - `<method_name>` at `<relative_file_path>` 2. <Subtask title and changes grouped by logical change>: - `<method_name>` at `<relative_file_path>` ... ### Notes: 1. <Note> 2. <Note> ### Estimation: [ ] <Subtask title matching numbered item>: <workdays> day(s) [ ] <Subtask title matching numbered item>: <workdays> day(s) ... [ ] Full integration testing: <workdays> days [ ] Buffer for unknowns: <workdays> days Implementation: <sum> workdays -> ~<weeks> weeks Testing & buffer: <sum> workdays -> ~<weeks> weeks Total: <sum> workdays -> ~<weeks> weeks -> ~<sprints> sprints ``` ## Rules 1. Technical Analysis section: One numbered item per logical change group. Each item has sub-bullets with the exact method name in backticks and