Summary

We are going to create a world of warcraft add on that finds the best talents and automatically enables them, with prompts to the user. We need to use the warcraftlogs to find the best M+ talents for each spec, and the best raid talents for each spec, and download them into a lua file that we can distribute with our add on. The addon should enable 'Loadouts' for the character, and when they enter a mythic level dungeon, or the current raid, it should select the appropriate talent. Note that there might be different best talents for different bosses in the raid - we will consider that a future feature. Ask me any questions you need answered, and create a ROADMAP.md file describing the work we are going to do to build this. Write the program to download content in python.

Now let me explore the project context and research the key technical areas in parallel.

I'll start by invoking the brainstorming skill since this is a new feature/project creation task.

Excellent research results. The project directory is empty (fresh start), and I now have a solid understanding of:

WarcraftLogs API v2: GraphQL-based, OAuth2 auth, has talentImportCode field in ReportFight data
WoW Talent API: C_ClassTalents.LoadConfig(), C_ClassTalents.ImportLoadout(), talent export strings
Event System: CHALLENGE_MODE_START for M+, ENCOUNTER_START for raids, ZONE_CHANGED_NEW_AREA for zone detection
Existing addons: BtWLoadouts, SwitchSwitch, TalentLoadoutManager — good reference implementations

Let me start with my first clarifying question:

Good — prompt-first approach. Next question:

Now I have enough context to design the architecture. Let me launch Plan agents to design the two major components.

Both design agents returned comprehensive plans. Let me update the task tracking and write the final plan.

Now let me write the comprehensive plan file.

Base directory for this skill: /mnt/dest-btrfs/home/jc/.claude/plugins/cache/claude-plugins-official/superpowers/4.3.0/skills/brainstorming

Brainstorming Ideas Into Designs

Overview

Help turn ideas into fully formed designs and specs through natural collaborative dialogue.

Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design and get user approval.

<HARD-GATE> Do NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action until you have presented a design and the user has approved it. This applies to EVERY project regardless of perceived simplicity. </HARD-GATE>

Anti-Pattern: "This Is Too Simple To Need A Design"

Every project goes through this process. A todo list, a single-function utility, a config change — all of them. "Simple" projects are where unexamined assumptions cause the most wasted work. The design can be short (a few sentences for truly simple projects), but you MUST present it and get approval.

Checklist

You MUST create a task for each of these items and complete them in order:

Explore project context — check files, docs, recent commits
Ask clarifying questions — one at a time, understand purpose/constraints/success criteria
Propose 2-3 approaches — with trade-offs and your recommendation
Present design — in sections scaled to their complexity, get user approval after each section
Write design doc — save to docs/plans/YYYY-MM-DD-<topic>-design.md and commit
Transition to implementation — invoke writing-plans skill to create implementation plan

Process Flow

dot

The terminal state is invoking writing-plans. Do NOT invoke frontend-design, mcp-builder, or any other implementation skill. The ONLY skill you invoke after brainstorming is writing-plans.

The Process

Understanding the idea:

Check out the current project state first (files, docs, recent commits)
Ask questions one at a time to refine the idea
Prefer multiple choice questions when possible, but open-ended is fine too
Only one question per message - if a topic needs more exploration, break it into multiple questions
Focus on understanding: purpose, constraints, success criteria

Exploring approaches:

Propose 2-3 different approaches with trade-offs
Present options conversationally with your recommendation and reasoning
Lead with your recommended option and explain why

Presenting the design:

Once you believe you understand what you're building, present the design
Scale each section to its complexity: a few sentences if straightforward, up to 200-300 words if nuanced
Ask after each section whether it looks right so far
Cover: architecture, components, data flow, error handling, testing
Be ready to go back and clarify if something doesn't make sense

After the Design

Documentation:

Write the validated design to docs/plans/YYYY-MM-DD-<topic>-design.md
Use elements-of-style:writing-clearly-and-concisely skill if available
Commit the design document to git

Implementation:

Invoke the writing-plans skill to create a detailed implementation plan
Do NOT invoke any other skill. writing-plans is the next step.

Key Principles

One question at a time - Don't overwhelm with multiple questions
Multiple choice preferred - Easier to answer than open-ended when possible
YAGNI ruthlessly - Remove unnecessary features from all designs
Explore alternatives - Always propose 2-3 approaches before settling
Incremental validation - Present design, get approval before moving on
Be flexible - Go back and clarify when something doesn't make sense

Here's a summary of the plan:

AzerothsTopTalent — Two components:

Python data pipeline (data_pipeline/) — Authenticates with WarcraftLogs API v2 (GraphQL, OAuth2), queries top-ranked players' characterRankings for all 39 specs across M+ and raid content, extracts talent import codes, picks the most popular build per spec, and generates a TalentData.lua file indexed by specID.
WoW Lua addon (AzerothsTopTalent/) — 7 files: TalentData (data), ImportExport (deserialize talent strings), LoadoutManager (apply talents via C_Traits API without consuming loadout slots), ContentDetector (detect M+ via CHALLENGE_MODE_START, raids via zone/encounter events), PromptUI (StaticPopup confirmation dialog), Settings (SavedVariables + panel), Core (orchestration + combat queueing).

Key decisions baked in from your answers:

Prompt before switching (with "Don't Ask Again" option)
Top rankings popularity approach for determining best builds
Pre-baked Lua data file shipped with addon
All 39 specs from day one

13 implementation steps, from scaffolding through to ROADMAP.md creation.

Now let me save this to plan.md in the project directory as requested.

Plan saved to /mnt/dest-btrfs/home/jc/src/azerothtoptalent/plan.md. Ready for approval.

Request interrupted by user for tool use

Let me start by exploring the project context and researching the key technical areas.

Designing WoW Add-on for Best Talent Selection

Designing WoW Add-on for Best Talent SelectionPublic