| name | isai-story-builder |
| description | Build and email ISAI sprint stories using the firm's standard story template. Use when asked to create, format, or email a sprint story, work item, or task for the ISAI team. Handles single stories or multi-story sprints. Fields include Story Title, Work Type, Description, Business Unit, Business Owner, Technical Owner, Platform, Hosting Model, Scope, Out of Scope, Assumptions, Dependencies, Data Classification, AI Model Involved, Vendor Risk Reviewed, Story Points, and Definition of Done. Triggers on phrases like "create a story", "build a sprint story", "write a work item", "format a story", "email a story", or any request to produce an ISAI-formatted story or task.
|
ISAI Story Builder
Produce correctly formatted ISAI sprint stories and optionally email them via msmtp.
Template Reference
See references/story-template.md for the full field reference, example story, and email format.
Template Fields
Jira Story Title:
Description:
Implementation:
Definition of Done (DOD):
Story Points:
Operations Readiness:
- Will there be Operations Training?
- Should an Operations Story be created?
- Will Operations support the Completed Product?
Optional Notes:
See references/story-template.md for full field guidance and a complete example.
Workflow
1. Gather Inputs
Collect from the user (or infer from context):
- Required: Jira Story Title, Description
- Recommended: Implementation steps, Definition of Done, Story Points
- Always include: Operations Readiness — all three questions must be answered or marked TBD
- Optional Notes: use for dependencies, data classification, AI model involvement, risks, assumptions
If the user provides a rough description, extract and structure the fields. Do not ask for fields that can be reasonably inferred.
2. Build the Story
Use the exact field order from the template. Format as plain text with field labels followed by values. Lists use - item bullets.
For multiple stories, build each in sequence and clearly separate them (Story 1 of N, etc.).
3. Show Before Sending
Always display the formatted story before emailing. Confirm the user is satisfied.
4. Email (if requested)
Use msmtp (config at ~/.msmtprc):
printf "From: openclaw@isms-cloud.com\nTo: <recipient>\nSubject: [ISAI Story] <Title>\n\n<body>" | msmtp <recipient>
Default sender: openclaw@isms-cloud.com
Ask the user for recipients if not specified.
Story Points Guide
| Points | Effort |
|---|
| 1–2 | Small — communication, simple report |
| 3 | Medium — analysis + output |
| 5 | Large — multi-step, stakeholder coordination |
| 8–13 | Epic-sized — break into smaller stories |
Definition of Done Defaults
Reporting / Operations:
- Analysis completed using latest data
- Output reviewed and approved
- Delivered to intended audience
- Feedback captured and documented
- Action items tracked and assigned
- Artifacts stored in governance repository
Communication:
- Drafted and reviewed
- Sent to all intended recipients
- Delivery confirmed
Development:
- Built and tested
- Reviewed and merged
- Documentation updated
- Stakeholder sign-off obtained
