Write or edit local user story markdown files that sync with Azure DevOps. Use when creating new user stories, editing existing stories, or when asked to write acceptance criteria. Stories are stored in docs/user-stories/{id}.md and synced via MCP sync tools.
User stories sync between local markdown files and Azure DevOps. Follow this exact format for successful push/pull cycles.
When pointed at an existing user story file, automatically fix all formatting issues without asking. Apply these fixes:
| Find | Replace With |
|---|---|
(To be defined) |  |
[To be defined] or similar |  |
Keep these helpful reminder patterns - they list commonly forgotten items:
- (e.g.: SPO set up, Customer Insights configured, outgoing mailboxes defined & available, etc.)
These reminders should only be removed:
If the section has ONLY the example reminder (no real content), add a TODO badge ABOVE it:
## Prerequisites
- (e.g.: SPO set up, Customer Insights configured, outgoing mailboxes defined & available, etc.)
| Find | Replace With |
|---|---|
[#1234](https://dev.azure.com/...) | #1234 |
[#1234](full-ado-url) | #1234 |
ADO auto-links #ID format and shows title/status - no need for full URLs.
- )##, subsections ###)/ado-push-items <id> or the sync-work-item-from-file MCP tooldocs/user-stories/{id}.md where {id} is the ADO work item ID.
---