feature-analyzerlisted

<SUBAGENT-STOP> If you were dispatched as a subagent to execute a specific task, skip this skill entirely. This skill is for orchestrators and interactive session-level routing only. Proceed directly with your assigned task. </SUBAGENT-STOP> # Feature Analyzer ## ⚠️ MANDATORY: DO NOT PROCEED WITHOUT CONTEXT **CRITICAL RULE: You CANNOT start analysis until user explicitly provides:** 1. ✅ Source repository (local path) 2. ✅ Target repository (local path) 3. ✅ Branch to analyze 4. ✅ Confirmation of analysis scope **DO NOT assume defaults. DO NOT use current directory. DO NOT proceed without asking.** **If user says:** "Analyze everything related to variables in pipelines" **You MUST respond:** ``` I'll help you analyze variables in pipelines. First, I need to clarify the context: **SOURCE Repository** (where the changes exist): - Local path: [user must provide, e.g., /Users/.../<PROJECT>] - GitHub repo: [owner/repo] - Branch to analyze: [branch-name] **TARGET Repository** (where implementation will happen): - Local path: [user must provide, e.g., /Users/.../<PROJECT>] - GitHub repo: [owner/repo] - Current branch: [branch-name] **FOCUS** (from your request): "variables in pipelines" - Keywords: variable, pipeline, param Once you provide these details, I'll begin the focused analysis. ``` **If user doesn't provide all required info → STOP and ask again.** --- ## Purpose Performs deep cross-repository analysis to understand business logic, architecture, API contracts