Roadmap

##Code Inspections

Using a tree structure representing the code, Rubberduck will be able to inspect VBA code and make suggestions on naming and code constructs being used, recommend refactorings and point out issues such as dead code, unused variables and members, etc.

Use the Code Inspections label.

##Refactorings

Using a tree structure representing the code in the IDE, Rubberduck will be able to implement a number of refactoring techniques, such as Rename, Extract Procedure, Extract Class, Extract Interface, Extract Module, Extract Variable, Encapsulate Field, Add/Remove Parameter, Decompose Conditional, Preserve Whole Object, Move Procedure, Introduce Parameter Object, Inline Class, Inline Procedure, Inline Temp, Introduce Assertion, ...and possibly more.

Use the Refactorings label for all issues related to refactorings.

##Source Control Integration Rubberduck will provide features to integrate the VBA IDE with GitHub, automatically exporting and importing code files to and from a local repository, separate from the Excel workbook, Word document, PowerPoint presentation, Access database, or Outlook session that contains the code.

Use the Source Control Integration label.

##Export XML Documentation

Add an option to parse all project, the current project, or a code module and export XML documentation of the VBA code. This will most likely use '@Attributes similar to the Unit Testing's '@TestMethod attributes, but this is yet to be determined.

Use the XML Documentation label for all related issues.

##Snippets

On a key shortcut, pop up an intellisense like menu for inserting user defined snippets of code. How these will be stored and edited is yet to be determined.

Use the Code Snippets label.