Azure DevOps Work Items by charlesjones-dev/claude-code-plugins-dev
npx skills add https://github.com/charlesjones-dev/claude-code-plugins-dev --skill 'Azure DevOps Work Items'此技能在使用 Azure DevOps MCP 服务器工具时,为创建和管理 Azure DevOps 工作项提供指导。它确保工作项遵循组织在层次结构、格式、命名约定和工时估算方面的最佳实践。
此技能应在以下情况下使用:
@azure-devops/mcp MCP 服务器工具时Azure DevOps 为敏捷项目使用三级结构:
关键规则:
关键: 所有文本字段必须使用正确的 HTML 格式,以确保在 Azure DevOps 中正确渲染。
示例:
<!-- 良好:正确的 HTML -->
<p>作为一名开发者,我需要实现用户身份验证。</p>
<p><strong>背景:</strong></p>
<ul>
<li>当前系统没有身份验证</li>
<li>用户需要安全的登录</li>
</ul>
<!-- 不佳:纯文本 -->
作为一名开发者,我需要实现用户身份验证。
背景:
- 当前系统没有身份验证
- 用户需要安全的登录
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
HTML 格式指南:
<p> 标签表示段落<ul> 和 <li> 表示项目符号列表<ol> 和 <li> 表示编号列表<strong> 表示粗体文本<em> 表示斜体文本<h3>、<h4> 表示章节标题目的: 包含相关用户故事的高级业务能力或目标。
描述字段:
<p> 标签和列表的 HTML 格式特性示例:
标题:1:用户身份验证系统
描述:
<p>实现一个完整的用户身份验证系统,包含登录、注册和密码重置功能。</p>
<p><strong>业务价值:</strong></p>
<ul>
<li>实现对应用程序的安全访问</li>
<li>支持个性化的用户体验</li>
<li>满足安全合规要求</li>
</ul>
字段设置:
目的: 从用户角度描述的特定功能,包含实现任务。
使用以下结构的 HTML 格式:
<p><strong>作为</strong> [用户角色],<strong>我想要</strong> [能力],<strong>以便</strong> [收益]。</p>
<p><strong>背景:</strong></p>
<ul>
<li>[背景要点 1]</li>
<li>[背景要点 2]</li>
<li>[背景要点 3]</li>
</ul>
<p><strong>附加信息:</strong></p>
<ul>
<li>[实现细节 1]</li>
<li>[实现细节 2]</li>
</ul>
示例:
<p><strong>作为</strong> 网站访客,<strong>我想要</strong> 注册一个账户,<strong>以便</strong> 我可以访问个性化功能。</p>
<p><strong>背景:</strong></p>
<ul>
<li>当前系统没有用户账户</li>
<li>市场团队需要用户追踪</li>
<li>未来功能依赖于用户身份</li>
</ul>
<p><strong>附加信息:</strong></p>
<ul>
<li>电子邮件应作为唯一标识符</li>
<li>需要密码强度验证</li>
<li>对于 MVP,建议进行电子邮件验证但非必需</li>
</ul>
使用带有 HTML 的 "Given, When, Then" 格式:
<p><strong>场景 1:成功注册</strong></p>
<ul>
<li><strong>Given</strong> 我在注册页面上</li>
<li><strong>When</strong> 我输入有效的电子邮件和密码</li>
<li><strong>Then</strong> 我的账户被创建并且我已登录</li>
</ul>
<p><strong>场景 2:无效电子邮件</strong></p>
<ul>
<li><strong>Given</strong> 我在注册页面上</li>
<li><strong>When</strong> 我输入无效的电子邮件格式</li>
<li><strong>Then</strong> 我看到错误消息并且无法提交</li>
</ul>
指南:
将斐波那契数列值应用于 "故事点" 字段,以估算相对复杂度:
字段设置:
目的: 轻量级工作跟踪项,代表独立的实现活动。
保持任务标题简单且描述性强,专注于工作活动:
良好的任务标题:
不佳的任务标题:
任务是工时跟踪的主要容器。将两个字段设置为相同的估算值:
示例:
原始估算:4
剩余工作:4
已完成工作:
估算指南:
字段设置:
Azure DevOps 缺乏强大的优先级排序功能,因此命名约定可确保在待办事项列表中的正确组织。
格式: [数字]: [描述]
示例:
有两种支持的命名约定。在创建用户故事之前,请检查项目的 CLAUDE.md 文件以了解配置的约定,或询问应使用哪种约定。
格式: [特性数字].[故事数字]: [描述]
示例:
优点:
格式: [描述]
示例:
优点:
格式: [描述]
示例:
创建工作项时,除非另有明确指定,否则应用以下默认值:
所有工作项类型:
项目特定值: 这些通常在项目的 CLAUDE.md 文件中配置:
当要求创建具有完整分解的新特性时:
当要求向现有故事添加任务时:
当用户故事过大时:
特性:1:用户身份验证系统
描述:<p>实现完整的用户身份验证...</p>
用户故事:1.1:用户注册
描述:<p><strong>作为</strong> 网站访客...</p>
验收标准:<p><strong>场景 1...</strong></p>
故事点:5
任务:实现注册 API 端点
原始估算:4
剩余工作:4
任务:创建注册表单 UI
原始估算:3
剩余工作:3
任务:为注册编写单元测试
原始估算:2
剩余工作:2
用户故事:1.2:用户登录
描述:<p><strong>作为</strong> 注册用户...</p>
验收标准:<p><strong>场景 1...</strong></p>
故事点:3
任务:实现登录 API 端点
原始估算:3
剩余工作:3
任务:创建登录表单 UI
原始估算:2
剩余工作:2
问题: 工作项未在待办事项列表中正确排序
解决方案: 确保特性编号为 1-99,并且用户故事遵循配置的命名约定。
问题: 验收标准在 Azure DevOps 中渲染不正确
解决方案: 验证所有文本字段是否使用正确的 HTML 格式。
问题: 任务在查询中显示为孤立项
解决方案: 验证每个任务在创建时是否设置了正确的父用户故事链接。
问题: 故事点在特性级别未正确求和
解决方案: 确保故事点仅设置在用户故事上,而非特性或任务上。
每周安装
0
仓库
GitHub 星标数
28
首次出现
1970年1月1日
安全审计
This skill provides guidance on creating and managing Azure DevOps work items when using the Azure DevOps MCP server tools. It ensures work items follow organizational best practices for hierarchy, formatting, naming conventions, and hour estimation.
This skill should be used when:
@azure-devops/mcp MCP server toolsAzure DevOps uses a three-level structure for Agile projects:
Key Rules:
CRITICAL: All text fields (Description, Acceptance Criteria) must use proper HTML formatting for correct rendering in Azure DevOps.
Examples:
<!-- Good: Proper HTML -->
<p>As a developer, I need to implement user authentication.</p>
<p><strong>Background:</strong></p>
<ul>
<li>Current system has no authentication</li>
<li>Users need secure login</li>
</ul>
<!-- Bad: Plain text -->
As a developer, I need to implement user authentication.
Background:
- Current system has no authentication
- Users need secure login
HTML Formatting Guidelines:
<p> tags for paragraphs<ul> and <li> for bullet lists<ol> and <li> for numbered lists<strong> for bold text<em> for italic text<h3>, <h4> for section headers (if needed)Purpose: High-level business capability or objective containing related User Stories.
Description Field:
<p> tags and listsExample Feature:
Title: 1: User Authentication System
Description:
<p>Implement a complete user authentication system with login, registration, and password reset capabilities.</p>
<p><strong>Business Value:</strong></p>
<ul>
<li>Enable secure access to the application</li>
<li>Support personalized user experiences</li>
<li>Meet security compliance requirements</li>
</ul>
Field Settings:
Purpose: Specific functionality described from a user perspective, containing implementation Tasks.
Use HTML formatting with this structure:
<p><strong>As a</strong> [user persona], <strong>I want to</strong> [capability], <strong>so that</strong> [benefit].</p>
<p><strong>Background:</strong></p>
<ul>
<li>[Context point 1]</li>
<li>[Context point 2]</li>
<li>[Context point 3]</li>
</ul>
<p><strong>Additional Information:</strong></p>
<ul>
<li>[Implementation detail 1]</li>
<li>[Implementation detail 2]</li>
</ul>
Example:
<p><strong>As a</strong> website visitor, <strong>I want to</strong> register for an account, <strong>so that</strong> I can access personalized features.</p>
<p><strong>Background:</strong></p>
<ul>
<li>Current system has no user accounts</li>
<li>Marketing team requires user tracking</li>
<li>Future features depend on user identity</li>
</ul>
<p><strong>Additional Information:</strong></p>
<ul>
<li>Email should be the unique identifier</li>
<li>Password strength validation required</li>
<li>Email verification recommended but not required for MVP</li>
</ul>
Use the "Given, When, Then" format with HTML:
<p><strong>Scenario 1: Successful Registration</strong></p>
<ul>
<li><strong>Given</strong> I am on the registration page</li>
<li><strong>When</strong> I enter valid email and password</li>
<li><strong>Then</strong> my account is created and I am logged in</li>
</ul>
<p><strong>Scenario 2: Invalid Email</strong></p>
<ul>
<li><strong>Given</strong> I am on the registration page</li>
<li><strong>When</strong> I enter an invalid email format</li>
<li><strong>Then</strong> I see an error message and cannot submit</li>
</ul>
Guidelines:
Apply Fibonacci sequence values to the "Story Points" field to estimate relative complexity:
Field Settings:
Purpose: Lightweight work tracking items representing individual implementation activities.
Keep Task titles simple and descriptive, focused on the work activity:
Good Task Titles:
Bad Task Titles:
Tasks are the primary container for hour tracking. Set both fields to the same estimated value:
Example:
Original Estimate: 4
Remaining Work: 4
Completed Work: (empty)
Estimation Guidelines:
Field Settings:
Azure DevOps lacks robust priority sorting, so naming conventions ensure proper organization in the backlog.
Format: [NUMBER]: [DESCRIPTION]
Examples:
There are two supported naming conventions. Check the project's CLAUDE.md file for the configured convention, or ask which convention to use before creating User Stories.
Format: [FEATURE_NUMBER].[STORY_NUMBER]: [DESCRIPTION]
Examples:
Benefits:
Format: [DESCRIPTION]
Examples:
Benefits:
Format: [DESCRIPTION]
Examples:
When creating work items, apply these defaults unless explicitly specified otherwise:
All Work Item Types:
Project-Specific Values: These are typically configured in the project's CLAUDE.md file:
Check Configuration First: Before creating work items, check if the project has Azure DevOps configuration in CLAUDE.md that specifies organization, project, team, area path, iteration path, and naming convention preferences.
Always Use HTML: Never use plain text or markdown in Description or Acceptance Criteria fields - always use proper HTML formatting.
Maintain Hierarchy: Never create orphaned work items. Every User Story needs a parent Feature, every Task needs a parent User Story.
Check Naming Convention: If not specified in CLAUDE.md, ask which naming convention is preferred (decimal notation like 1.1, 1.2 or simple descriptive names) before creating User Stories.
Keep Tasks Lightweight: Tasks should not duplicate the User Story's description or acceptance criteria. They should be simple work containers with just a title and hour estimates.
Leave Assignments Blank: Let team members assign themselves to work items during sprint planning or daily standups.
Estimate Realistically: Include time for testing, code review, documentation, and debugging in task hour estimates.
Use Story Points Consistently: Apply Fibonacci sequence values to User Stories based on relative complexity, not absolute time.
Progressive Disclosure: Create Features first, then User Stories, then Tasks. This allows for iterative refinement of scope and estimation.
Validate Before Creating: Review the work item hierarchy and ensure all required fields are populated before calling MCP tools to create items.
When asked to create a new feature with full breakdown:
When asked to add tasks to an existing story:
When a User Story is too large (Story Points 13+):
Feature: 1: User Authentication System
Description: <p>Implement complete user authentication...</p>
User Story: 1.1: User Registration
Description: <p><strong>As a</strong> website visitor...</p>
Acceptance Criteria: <p><strong>Scenario 1...</strong></p>
Story Points: 5
Task: Implement registration API endpoint
Original Estimate: 4
Remaining Work: 4
Task: Create registration form UI
Original Estimate: 3
Remaining Work: 3
Task: Write unit tests for registration
Original Estimate: 2
Remaining Work: 2
User Story: 1.2: User Login
Description: <p><strong>As a</strong> registered user...</p>
Acceptance Criteria: <p><strong>Scenario 1...</strong></p>
Story Points: 3
Task: Implement login API endpoint
Original Estimate: 3
Remaining Work: 3
Task: Create login form UI
Original Estimate: 2
Remaining Work: 2
Problem: Work items not appearing in the correct order in backlog
Solution: Ensure Features are numbered 1-99, and User Stories follow the configured naming convention (decimal notation or descriptive names).
Problem: Acceptance criteria rendering incorrectly in Azure DevOps
Solution: Verify all text fields use proper HTML formatting with <p>, <ul>, <li> tags.
Problem: Tasks showing as orphaned in queries
Solution: Verify each Task has a parent User Story link set correctly when created.
Problem: Story Points not summing correctly at Feature level
Solution: Ensure Story Points are only set on User Stories, not on Features or Tasks.
Weekly Installs
0
Repository
GitHub Stars
28
First Seen
Jan 1, 1970
Security Audits
Azure Data Explorer (Kusto) 查询技能:KQL数据分析、日志遥测与时间序列处理
114,200 周安装