mirror of
https://github.com/EveryInc/compound-engineering-plugin.git
synced 2026-09-19 01:09:55 +08:00
7cfd93a3b5
PR #826 refactored the requirements-grouping rule into the new section contract and rendering references, and in the move dropped its strongest framing. The rule flipped from default-on ("skip grouping only when all requirements are about the same thing") to a positive conditional ("group when they span distinct concerns"), which hands the agent an easy out: judge a long set as "one concern" and emit a flat list while feeling compliant. A 14-requirement flat list slipped through as a result. Restore the default-on test across both skills: - brainstorm-sections.md / plan-sections.md: add back "skip grouping only when all requirements are genuinely about the same thing; a long flat list is a smell that subgroups were missed", and restore the "not item count" emphasis to the brainstorm copy so both contracts match. - markdown-rendering.md (both): reframe grouping from optional ("group when...") to the default shape for multi-concern requirement sets. - html-rendering.md (both): make concern-grouping take precedence over the flat-<table> default so a multi-concern set renders as grouped tables rather than one flat table. - brainstorm-sections.md: align the agency back-pointer, which still restated the old weak conditional and contradicted the strengthened Hard Floor text in the same file.