story-writing

Format Azure DevOps work items with markdown templates and acceptance criteria.

Updated Dec 5, 2025

Search Tags:#issue management #bug report #user stories #azure devops #work items

Ready to run

npx skills add https://github.com/mpetito/prompts --skill story-writing-mpetito

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: story-writing
Source: https://github.com/mpetito/prompts/tree/main/skills/story-writing
Command: npx skills add https://github.com/mpetito/prompts --skill story-writing-mpetito

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of crafting well-structured Azure DevOps work items, enabling teams to define tasks, issues, and bugs with clear formatting and measurable acceptance criteria.

Core Features & Use Cases

Work Item Structuring: Guides users to select the appropriate work item type and fill in mandatory fields accurately.
Formatting Standards: Provides markdown templates for user stories, issues, and bugs to ensure clarity and consistency.
Use Case: For a development team preparing a sprint backlog, quickly generate properly formatted user stories and acceptance criteria to facilitate smooth planning and execution.

Quick Start

Ask the AI to help create a new user story for adding a login feature in the app.

Frequently Asked Questions about story-writing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I format Azure DevOps user stories to ensure clear acceptance criteria?▼

Format Azure DevOps user stories by applying structured markdown templates that guide accurate field completion and generate measurable acceptance criteria. This ensures detailed requirement documentation and improves project tracking clarity for development teams.

What is the best way to structure Azure DevOps bug reports for sprint planning?▼

The best way to structure Azure DevOps bug reports is using standardized markdown formatting to define mandatory fields accurately. This creates consistent issues and work items, facilitating smoother sprint backlog planning and execution.

How does markdown formatting improve Azure DevOps work item tracking?▼

Markdown formatting improves Azure DevOps work item tracking by enforcing structured content and process compliance. This standardizes issues, bugs, and user stories, making requirements highly readable and measurable for project management.

Can I use this to generate work items for an Azure DevOps sprint backlog?▼

Yes, you can generate properly formatted work items for an Azure DevOps sprint backlog. It helps quickly define user stories, issues, and bugs with detailed acceptance criteria, facilitating smooth sprint planning and team execution.

Do I need a specific Azure DevOps setup to create structured work items?▼

No specific Azure DevOps setup is required to create structured work items. The process focuses on generating markdown-formatted content and defining measurable acceptance criteria that you can then copy into your existing project management workflows.

Why are my Azure DevOps user stories missing measurable acceptance criteria?▼

Azure DevOps user stories often lack measurable acceptance criteria due to unstructured inputs. Applying standardized markdown templates ensures proper field completion and enforces detailed, measurable criteria for better requirement documentation.