As Tom mentioned, I developed a point form narrative for myself totally manually, simply by changing the sentence templates for the 15 or 20 fact types that I most commonly use. Tom's efforts are much more ambitious, using an automated process to change the sentence templates for all the fact types in your RM database, and then allowing you an easy way to change back. Tom's efforts bring up an interesting point that might be pertinent at this time, especially since the total rewrite for RM is said to include a significant revamping of RM's report engine.
The interesting point is that your RM database only includes a single sentence template for each of your fact types. Suppose you wanted to run standard narrative reports on Mondays, Wednesdays, and Fridays and suppose you wanted to run point form narrative reports on Tuesdays and Thursdays. And further suppose that for whatever reason, you didn't want to run Tom's SQLite script to switch back and back and forth. Under these circumstances, you only recourse would be to spend a lot of time each morning manually editing a bunch of sentence templates to switch between your Monday/Wednesday/Friday style of sentence templates and your Tuesday/Thursday style of sentence templates.
I think instead that RM should support multiple sets of sentence templates. In practice, this would probably mean having multiple copies of RM's FactTypeTable, with each copy of the FactTypeTable implementing a particular report style. And these multiple copies of RM's FactTypeTable should be exposed to the user interface so the user could easily choose standard style or point form style. But why stop at two styles. Why not have a verbose style and a terse style and a German style and a Spanish style, etc. in addition to the standard and point form styles. And why not arrange things so that users could exchange report styles that they might have developed. I would point out in this regard that RM's present design doesn't even allow you to Drag and Drop a copy of your database to yourself while maintaining any customizations you have made to the built-in sentence templates in the FactTypeTable. So today, you can't even carry over a report style that you develop to another copy of your database that you make with Drag and Drop.
Finally, RM's FactTypeTable is not just about sentence templates. It's also about which fact types are included in which kinds of reports (GEDCOM export, narrative reports, family group sheets, etc.), it's about which fact types have dates or descriptions or places, etc. These attributes of the FactTypeTable would also benefit greatly from having multiple styles with the styles being exposed to the user interface. For example, one style might export one list of facts in GEDCOM and another style might export a different list of facts in GEDCOM. At the present time, adjusting the list of fact types to be exported to suit your intended audience is a very major pain.
I'm sure I have written about multiple report styles before. But given the rewrite of RM's report engine and given Tom's really wonderful SQLite script to automate the process of producing point form reports, I think it's a good time to bring up once again the idea of RM supporting different styles for the FactTypeTable.
If you haven't looked at any point form reports, I think they look pretty nice - even if I do say so myself. They are not just individual summaries or family group sheets stuffed into the format of a narrative report. Indeed, they can contain a great deal of narrative if you have a lot of information included in notes, despite how terse the presentation is for the basic facts. I posted an example of a real report done in this style in my original posting on this subject which in turn was cited by Tom. I'm sure that the point form report style will not be for everybody, but if you wish you can see an example of such a report without having to create one for yourself.