aio-planlisted

# Plan — Implementation Planning ## Environment - GitNexus: !`npx gitnexus status 2>/dev/null && echo "AVAILABLE" || echo "NOT INSTALLED"` Synthesize discovery and mapping results into a concrete, actionable implementation plan. ## Prerequisites - Run `/discover` and `/map` first (or have equivalent understanding) - GitNexus indexed (`npx gitnexus analyze`) for convention/duplication checks ## Workflow ### Step 1: Duplication check (GitNexus) Search if similar features already exist using the GitNexus MCP `query` tool: ``` query("similar feature or pattern") ``` Prevents building what already exists. ### Step 2: Convention check (GitNexus) Search for existing patterns to follow: ``` query("how are [similar things] implemented") ``` Examples: "tauri command structure", "hook cleanup pattern", "error handling in rust" ### Step 3: Context enrichment (GitNexus) For each file you plan to modify, get full context: ``` context(file) ``` This reveals dependencies, dependents, and all symbols — helps identify: - Functions that will be affected by your changes - Files that import the file you're changing (blast radius) - Existing symbols you can reuse instead of creating new ones For the most critical change, check impact: ``` impact(file) ``` ### Step 4: Write the plan ``` ## Plan: [Feature/Fix Name] ### Goal [One sentence: what and why] ### Discovery Summary [Key findings from /discover] ### Approach [High-level strategy: which layer handles what] ### Changes