$ loading_
Configure a work item platform and detect Azure DevOps process templates.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "board-config" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/devsquad-copilot/main/.github/plugins/devsquad/skills/board-config/SKILL.md 2. Save it as ~/.claude/skills/board-config/SKILL.md 3. Reload skills and tell me it's ready
Help me configure the work item platform for this repository. The code repo is on GitHub, but I’m not sure whether requirements and bugs should go to GitHub Issues, Azure DevOps Boards, or only a local tasks.md.
A confirmed platform choice, with saved preferences such as repo platform and board platform.
We use Azure DevOps Boards. Please infer whether this project uses Scrum, Agile, Basic, or CMMI from existing work item types and record it in the configuration.
The matching process template is identified, with user confirmation if needed, and written to the config file.
First check whether this project already has a board-config. If it exists, report it directly; if only the repo platform is known, continue by helping me confirm the work item platform.
The current configuration status is reported, and the setup continues when information is incomplete.
Developers or product managers can use it when the code repository and work item system live on different platforms. It helps confirm whether work items should be managed in GitHub, Azure DevOps, or locally only.
When a team manages requirements and tasks in Azure DevOps, it can identify the current process template. This helps later work item operations use the right types and fields.
In an existing project, it first checks for a saved board-config and reuses it when possible. If the configuration is incomplete, it guides the user to fill in the missing details.
The documentation explains how to configure a project's work item platform. It starts by checking for an existing `.memory/board-config.md`, then confirms whether work items should be managed in GitHub Issues, Azure DevOps Boards, or a local `tasks.md`. If Azure DevOps is used, it detects the process template from existing work item types and saves the result. It also notes GitHub label pattern detection and common work item types and fields for each Azure DevOps template.
cat .memory/board-config.md 2>/dev/null
If Board Platform is filled in, use the configured platform. If only Repo Platform is filled in (hook seed), proceed to confirm board.
The repo and the board can be on different platforms. Ask the user:
Repo detected: [Repo Platform from config, or detect from remote]
Where do you want to manage work items?
[G] GitHub Issues
[A] Azure DevOps Boards
[L] Local only (tasks.md)
If Repo Platform is azdo, suggest Azure DevOps Boards as default. If github, ask the user (it could be GitHub Issues or Azure DevOps).
Search existing work items and identify by types:
| Type found | Template |
|---|---|
| Product Backlog Item | Scrum |
| User Story | Agile |
| Issue (without PBI/US) | Basic |
| Requirement | CMMI |
If there are no work items, ask the user.
Save to .memory/board-config.md:
# Board Config
Repo Platform: [github|azdo]
Board Platform: [github|azdo|local]
Azure DevOps URL: [url] (if applicable)
Process Template: [scrum|agile|basic|cmmi] (if Azure DevOps)
| Repository | Board | Action |
|---|---|---|
| GitHub | GitHub | Create issues on GitHub (default) |
| GitHub | Azure DevOps | Create work items on Azure DevOps |
| Azure DevOps | Azure DevOps | Create work items on Azure DevOps |
| Azure DevOps | GitHub | Create issues on GitHub |
| Any | Local | Generate tasks.md only |
type:bug, type:feature, priority:high are found, the project already has conventions| If found | Use pattern |
|---|---|
type:xxx or kind:xxx | Prefix type: or kind: |
priority:xxx or P1/P2/P3 | Same format found |
feature/xxx or feature:xxx | Same format found |
| No pattern | Use devsquad default: type:user-story, feature:<name> |
| Template | User Story Type | Task Type |
|---|---|---|
| Scrum | Product Backlog Item | Task |
| Agile | User Story | Task |
| Basic | Issue | Task |
| CMMI | Requirement | Task |
Scrum:
Agile:
Basic:
CMMI:
It configures the work item management platform, identifies GitHub Issues, Azure DevOps Boards, or local tasks.md, and saves the preference. It does not create work items or manage implementation workflow.
It infers the process template from existing work item types, such as Product Backlog Item for Scrum and User Story for Agile. If no work items exist, it needs the user to confirm.
The docs indicate the configuration is saved in `.memory/board-config.md`, including Repo Platform, Board Platform, and Azure DevOps details when applicable. For more details, see the source repository.
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.
Create well-structured issues, stories, tasks, epics, and features on boards.
Triages issues with label-driven state transitions and durable, resumable records.
Add Azure DevOps to Power Apps for work items, bugs, pipelines, and API calls.
Manage Productboard features, notes, objectives, components, and releases with natural language.
Manage Azure DevOps work items, sprints, and boards using natural language.
Lets AI manage Azure DevOps projects, repos, work items, PRs, and pipelines.