MicrosoftKnown publishermicrosoft/devsquad-copilot/.github/plugins/devsquad/skills/board-config/SKILL.mdboard-config
Skill50 starsChanged 16 days agoMITView on GitHub
Configure work item platform (GitHub Issues or Azure DevOps), detect process template, and save preference. Use when you need to identify where to create or read work items. Do not use for creating work items (use work-item-creation) or for managing implementation workflow (use work-item-workflow).
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
If Board Platform is filled in, use the configured platform.
- Very specific: line 30
If Repo Platform is azdo, suggest Azure DevOps Boards as default.
- Distinctive: line 34
Search existing work items and identify by types:
- Distinctive: line 43
If there are no work items, ask the user.
- Distinctive: line 72
Search existing issues to identify the label pattern used
- Very specific: line 73
If labels like type:bug, type:feature, priority:high are found, the project already has conventions
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Configure Board
1. Check existing config
cat .memory/board-config.md 2>/dev/nullIf Board Platform is filled in, use the configured platform. If only Repo Platform is filled in (hook seed), proceed to confirm board.
2. Confirm board platform
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).
3. If Azure DevOps, detect process template
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.
4. Save config
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)Supported Scenarios
| 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 |
GitHub Configuration
Check Existing Labels
- Search existing issues to identify the label pattern used
- If labels like
type:bug,type:feature,priority:highare found, the project already has conventions - Adapt generated labels to follow the existing pattern
Label Pattern Detection
| 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> |
Process Templates (Azure DevOps)
| Template | User Story Type | Task Type |
| Scrum | Product Backlog Item | Task |
| Agile | User Story | Task |
| Basic | Issue | Task |
| CMMI | Requirement | Task |
Required Fields by Template
Scrum:
- Product Backlog Item: Title, Description, Acceptance Criteria, Effort, Priority
- Task: Title, Description, Remaining Work, Activity
Agile:
- User Story: Title, Description, Acceptance Criteria, Story Points, Priority
- Task: Title, Description, Original Estimate, Remaining Work, Activity
Basic:
- Issue: Title, Description, Effort, Priority
- Task: Title, Description, Remaining Work
CMMI:
- Requirement: Title, Description, Size, Priority, Impact
- Task: Title, Description, Original Estimate, Remaining Work, Discipline
In this repository26 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- .github/plugins/devsquad/hooks/templates/.github/copilot-instructions.mdCopilot instructions
- adr-workflowSkill
- complexity-analysisSkill
- debugging-recoverySkill
- deep-clarificationSkill
- diagram-designSkill
- documentation-styleSkill
- domain-glossarySkill
- engineering-practicesSkill
- git-branchSkill
- git-commitSkill
- harness-learningsSkill
- init-configSkill
- init-docsSkill
- init-scaffoldSkill
- lsp-setupSkill
- next-taskSkill
- pull-requestSkill
- quality-gateSkill
- reasoningSkill
- security-reviewSkill
- test-disciplineSkill
- triage-workflowSkill
- work-item-creationSkill
- work-item-workflowSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.