What problem does it solve? When a design request would produce two or more related specs, teams often end up with flat sibling specs that have no shared parent and become hard to discover. This Skill provides the canonical doctrine and paste-ready phrasing for nudging users toward composing related specs into an initiative with phased children instead. ## Core Features & Use Cases - Canonical phrasing: Supplies one verbatim sentence quoted by both interactive triage (/roadmap-review) and design-time routing (/design) so the nudge wording stays consistent across surfaces. - Trigger rules: Defines three any-of triggers — explicit multi-deliverable phrasing, lead-identified sub-deliverables, and rolled-up size of large or higher — each sufficient to fire the nudge. - Precedence and suppression: Coordinates with the sizing nudge so exactly one nudge fires per moment, and suppresses re-firing inside /compose flows or after a session-level decline. - Use Case: A user asks to "design the checkout, cart, and payment specs." The lead quotes the trigger #1 phrasing, recommends /compose to scaffold an initiative with three child stubs, and proceeds based on the user's yes/no answer. ## Quick Start When a design request names multiple related deliverables, quote the canonical nudge sentence and ask whether to compose them into an initiative before writing sibling specs.
