notification-generator

To generate notification scenarios from user stories, provide a user_stories_data.json file to extract actors and events, map them to roles, and output a structured notification_scenarios.json file aligned with template references.

The best way to structure user stories for notification strategy is to define actors, events, and criteria in a JSON format, allowing automated tools to classify roles like end_user or provider and determine appropriate notification channels.

Mapping actors to abstract roles helps with notification channel configuration by categorizing users into end_user, provider, and operator groups, ensuring each role receives relevant communications through the most appropriate channels.

Yes, you can use custom templates for generating user story notification scenarios. The generator aligns its output with a provided template.json file and schema, ensuring consistent messaging structure across your product's notification strategy.

You need to provide user stories in a docs/user_stories_data.json file containing actors, user stories, and events. The generator reads this file, filters events by criteria, and outputs docs/notification_scenarios.json.

Generated notification scenarios might not match the expected template if the input user_stories_data.json lacks defined actors or events, or if the output is not properly validated against the provided template.json schema and event naming conventions.