$ loading_
帮助你规范创建 GitHub Issues 或 Azure DevOps 的任务、需求与史诗条目。
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "work-item-creation" 技能： 1. 下载 https://raw.githubusercontent.com/microsoft/devsquad-copilot/main/.github/plugins/devsquad/skills/work-item-creation/SKILL.md 2. 保存为 ~/.claude/skills/work-item-creation/SKILL.md 3. 装好后重载技能，告诉我可以用了
请根据以下需求创建一条 Azure DevOps 用户故事：作为一名新用户，我希望用邮箱和验证码注册账号，以便快速开始使用产品。请补充标题、描述、验收标准、优先级、标签和建议拆分任务。
一条结构完整的用户故事草稿，包含清晰字段和可执行的验收标准。
请把下面的问题整理成 GitHub Issue：用户在 Safari 浏览器提交付款时页面卡住，没有成功提示。已知影响 iOS 17，偶发，可能与 3D Secure 跳转有关。请输出标题、问题描述、复现步骤、实际结果、预期结果、影响范围和排查建议。
一条便于研发排查的缺陷工单，信息完整且便于直接提交。
我们准备上线“团队权限管理”能力，请为 Azure DevOps 先创建 1 个 Epic 和 3 个 Feature，分别覆盖角色定义、权限分配、审计日志。请给出每个条目的标题、业务目标、范围说明、关键依赖和完成标准。
一组层级清晰的史诗与功能项草稿，便于团队直接导入看板规划。
Before creating ANY work item, verify:
.memory/board-config.md to identify GitHub or Azure DevOpsWork items live on the board, get rendered in GitHub/ADO UIs, and are read by humans and agents long after creation. Apply these rules to every title, description, comment, and acceptance criterion.
| Rule | Why | Example to avoid |
|---|
| No emojis or decorative Unicode (e.g., →, •, ★, ✓, 🎯, ✅, ⚠️, ❌) | Renders inconsistently across boards, screen readers, and exports | 🎯 Goal: ship X |
| No em-dash (—), en-dash (–), or hyphen as separator between concepts | Ambiguous in titles, breaks search, often AI-generated tell. Rewrite the sentence. | Auth flow — refactor → Refactor auth flow |
Never use #<number> in free text | Azure DevOps auto-converts to a work item link, breaking references and creating wrong cross-links. Use "first", "third option", or rephrase. | #1 priority → top priority |
| No contrastive constructions ("not just X, it's Y", "more than just", "goes beyond") | Generic AI framing that adds words without information | This is not just a fix, it's a rethink → Replace the retry logic |
| Direct active voice, no rhetorical questions | Work items are commands or descriptions, not essays | What if we cached responses? We should cache them. → Cache responses for 60 seconds |
| No promotional or exaggerated language | Work items track work, not pitch it | seamless, revolutionary, world-class |
| Keep titles short and concrete; bodies focused on observable behavior | Titles surface in lists; bodies are read once during planning and again during review | See Durability Rules for body content rules |
These rules apply to content sent to GitHub Issues, Azure DevOps work items, board comments, PR descriptions written from a work item, and triage artifacts. They do not replace the markdown rules in the documentation-style skill, which still govern files under docs/**/*.md.
All generated work items must include the tag/label ai-model:<model-name>.
grep -h "Using.*model" ~/.copilot/logs/*.log 2>/dev/null | tail -1
cat ~/.copilot/config.json 2>/dev/null | grep -i model
ai-model:unknownBefore applying labels to a work item, check if they exist in the repository:
github/list_label(owner, repo)
If any required label does not exist, create it automatically via github/label_write:
| Label | Color (hex) |
|---|---|
copilot-generated | 1d76db |
ai-model:* | 5319e7 |
type:user-story | 0e8a16 |
type:task | 0e8a16 |
type:adr | 0e8a16 |
type:tech-debt | d93f0b |
feature:* | c5def5 |
priority:p1 | b60205 |
priority:p2 | fbca04 |
priority:p3 | 0e8a16 |
phase:* | bfdadc |
severity:high | b60205 |
severity:medium | fbca04 |
severity:low | 0e8a16 |
epic | 3e4b9e |
feature | c5def5 |
parallel | d4c5f9 |
blocked | b60205 |
copilot-candidate | 1d76db |
needs-human | e4e669 |
scope:cross-cutting | bfdadc |
scope:feature-scoped | bfdadc |
…
帮助你创建、切换并检查代码分支，确保实现前遵循正确分支策略。
为 Power Apps 代码应用接入 Azure DevOps 连接器，便于查询工单、提报缺陷与管理流水线。