Metteec,
I've seen the proliferation and sharing of clause matrices that included descriptions or highlights of what clauses to include and when. In most instances, those tools got users other than the creator into trouble. I imagine we could both agree that your clause book is imperfect, but since you created it, you're intimately familiar with any/all shortcomings so you know how to use it as effectively and as accurately as possible. Others that may use it will presumably have a more difficult time because they'll need to spend time familiarizing themselves with your format, choices, etc. which could lead to inaccuracies (at least that is what my observations have led me to believe thus far).
When I led the services/commodities flight at my previous base, I encouraged everyone to go through the process of creating their own personal tool for the clauses in FAR Subpart 12.3 and DFARS Subpart 212.3. For those that took the task seriously, they learned the method (and difficulties) of evaluating clauses and, after multiple iterations of feedback to increase the tool's accuracy, they arrived at a tool that they were familiar with and could use more easily than something passed on to them from another buyer or found on the web. Vern is right - going through the process to develop a tool/matrix is no easy task. A suitable one takes considerable time and effort, but in our case, we were limited to a microcosm of the FAR because we only dealt with commercial item acquisitions so that simplified everything considerably.
I think the goal of a "one tool to rule them all" is admirable, but frankly since tools are based on interpretation and descriptions, they'll likely be prone to the same difficulties as the ones that float around today. Such tools will likely be no better than reviewing the clause prescription itself (i.e. one person's plain English is not necessarily another person's plain English). For this reason, I primarily use the current matrix for the ability to quickly access prescriptions without having to comb through the FAR completely and create my own tools so I know what strengths/weaknesses are present (which minimizes the potential for errors) - I'd encourage others to do the same.