I think this suggestion of polishing the basic layer first and then building the high level layer is a good one. Since the potential development directions are

I think this suggestion of polishing the basic layer first and then building the high level layer is a good one. Since the potential development directions are so broad (marketplace for rule sets, evaluation of rule sets, version control of rule sets, more useful tools, unit test & deployment & PM rules), I have never dared to over-design before users have clear feedback. For project management, I have another exploratory project. This project is a set of rules that use Cursor/Cline/Windsurf as a project manager assistant. repo is here: https://github.com/botingw/pm-workflow-copilot-ide https://github.com/botingw/pm-workflow-copilot-ide For your 2, I understand versioning with rules. Does compose mean assembling rules? What does reasoned about mean? For your 3, what configuration management do you recommend adding?