$ loading_
Create well-structured issues, stories, tasks, epics, and features on boards.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "work-item-creation" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/devsquad-copilot/main/.github/plugins/devsquad/skills/work-item-creation/SKILL.md 2. Save it as ~/.claude/skills/work-item-creation/SKILL.md 3. Reload skills and tell me it's ready
Create an Azure DevOps user story from this requirement: As a new user, I want to sign up with email and verification code so I can start using the product quickly. Include a title, description, acceptance criteria, priority, tags, and suggested subtasks.
A complete user story draft with clear fields and actionable acceptance criteria.
Turn this problem into a GitHub Issue: users get stuck on the payment page in Safari and never see a success message. Known impact: iOS 17, intermittent, possibly related to the 3D Secure redirect. Output a title, description, reproduction steps, actual result, expected result, impact, and investigation notes.
A submission-ready bug issue with complete details for engineering investigation.
We are launching a team permission management capability. Create 1 Epic and 3 Features in Azure DevOps covering role definitions, permission assignment, and audit logs. Provide a title, business goal, scope, key dependencies, and definition of done for each item.
A clearly structured epic-and-feature set ready for board planning and import.
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 |
…
Design and review software architecture diagrams for clearer, documentation-friendly visuals.
Create, switch, and verify Git branches before starting implementation work.
Initialize projects or verify and generate up-to-date SDD documentation templates.
Verify and create standard community and governance files for new projects.
Verify assignee, dependencies, priority, and capacity before starting a work item.
Systematically triage failures and fix broken builds or unexpected runtime issues.
Triages issues with label-driven state transitions and durable, resumable records.
Turn conversations into epics, features, user stories, and tasks in Azure DevOps.
Generate standardized Git commits from diffs with logical grouping support.
Add Azure DevOps to Power Apps for work items, bugs, pipelines, and API calls.
Create and maintain ADRs with checks, references, and planning support.
Generate a structured .instructions.md file for project rules or conventions.