write-local-user-stories

To sync local user stories with Azure DevOps, you create Markdown files with required frontmatter under docs/user-stories and use MCP tooling to push and pull data. This enforces a strict file structure to reduce manual rework and data drift.

The required frontmatter format for local user stories is a strict Markdown structure stored as docs/user-stories/{id}.md. This Skill validates and auto-fixes the file layout to ensure stories remain machine-readable and human-friendly.

You can auto-fix acceptance criteria formatting in Markdown user stories by applying this Skill's validation rules. It automatically corrects Given/When/Then structures and prerequisites to ensure consistency across all local story files.

Yes, you can use MCP tooling to push local Markdown user stories to Azure DevOps. This Skill supports an end-to-end workflow that synchronizes your locally authored story files with your Azure DevOps project.

To avoid treating template placeholders as client requirements, this Skill includes built-in templates and best-practices guidelines. These ensure you distinguish between structural boilerplate and actual project requirements during story creation.

A limitation of syncing Markdown user stories with Azure DevOps is the strict dependency on the exact docs/user-stories/{id}.md frontmatter structure. Deviating from this enforced layout will prevent proper synchronization and auto-fixing.