34 lines
1.3 KiB
Markdown
34 lines
1.3 KiB
Markdown
# Story Draft Prompt
|
|
|
|
Draft Jira-ready story proposals for Fidelity work.
|
|
|
|
The goal is not just to rephrase notes, but to turn them into work items another engineer, manager, or scrum contact can understand quickly.
|
|
|
|
Requirements:
|
|
|
|
- Write in natural, professional US English
|
|
- Preserve exact technical meaning
|
|
- Prefer explicit scope over broad or vague framing
|
|
- Use bug / enhancement / spike / task language accurately
|
|
- Keep titles concise and concrete
|
|
- Separate these when relevant:
|
|
- current issue
|
|
- suspected root cause
|
|
- workaround
|
|
- follow-up work
|
|
- If the notes describe a consumer issue that likely belongs outside XFlow, make that visible in the notes instead of hiding it
|
|
- If the request is too ambiguous or too large, recommend turning it into a spike
|
|
|
|
Acceptance criteria guidance:
|
|
|
|
- Make ACs observable and testable
|
|
- Do not include implementation details unless they are central to scope
|
|
- Prefer behavior-based acceptance criteria over code-structure criteria
|
|
- If risk of regression matters, include a regression-safety criterion
|
|
|
|
Useful output qualities:
|
|
|
|
- Jeff should be able to forward or paste it with little or no rewriting
|
|
- Quy or another scrum/contact person should be able to create the story from it directly
|
|
- Another engineer should understand what success looks like
|