aifollowup

Generate follow-up questions by cross-considering unstaged changes, current non-master commits, and the todo roadmap to produce exactly three concise questions oriented around design issues, implementation problems, and bottleneck investigation.

Follow-up questions in software design are used to surface design tradeoffs, implementation risks, and overlooked constraints that only become clear by extending reasoning from current unstaged changes and recent commits during active development work.

Identify implementation risks and performance bottlenecks by analyzing non-master branch commits and unstaged changes against the todo roadmap, producing targeted questions that reveal where architecture, performance, or correctness assumptions may break down.

Yes, you can use commit analysis to check if your refactoring breaks architecture assumptions by extending reasoning from your recent commits and unstaged changes to quickly identify where correctness assumptions are failing as you move forward.

Yes, follow-up question generation works specifically with unstaged changes and non-master branch commits, cross-considering these elements alongside the todo roadmap so that the resulting questions align with what is actually happening next in your workflow.

The best way to surface design tradeoffs during active development is to generate exactly three concise follow-up questions oriented around design issues, implementation problems, and bottleneck investigation by cross-considering your current commits and todo roadmap.