$ loading_
Verify assignee, dependencies, priority, and capacity before starting a work item.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "work-item-workflow" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/devsquad-copilot/main/.github/plugins/devsquad/skills/work-item-workflow/SKILL.md 2. Save it as ~/.claude/skills/work-item-workflow/SKILL.md 3. Reload skills and tell me it's ready
Please follow the work-item implementation workflow for this GitHub issue: confirm whether I am the assignee, list blocking dependencies, assess the current priority, and evaluate whether I should start now based on my in-progress workload.
A pre-start checklist result with assignee confirmation, dependency list, priority assessment, and a recommendation on whether to start now.
Please review whether this Azure DevOps work item is ready for immediate implementation in this sprint: verify the assignee, prerequisite tasks, business priority, and whether current team capacity supports taking it on.
An implementation-readiness assessment explaining whether the work item can move into development now and why.
Using this work item information, run a pre-start review: check whether an assignee is missing, whether unfinished dependencies exist, whether the priority is high enough, and whether my capacity allows parallel work.
A summary of risks and blockers highlighting missing information, potential conflicts, and recommended next actions.
Analyze the user's input to determine the source:
.memory/board-config.md or detect from remote (git config --get remote.origin.url)gh api user --jq '.login'az account show --query user.name -o tsv or ask the userExecute in order. If any check blocks, STOP and inform the user.
| Situation | Action |
|---|---|
| Assigned to another dev | STOP: "Work item already assigned to [name]." |
| No assignee | Assign current user (see below), then inform: "Assigned this task to you." |
| Assigned to the current user | Proceed |
When the work item has no assignee, do not skip this step. Execute the assignment before moving to the State update check:
github/issue_write with method: "update", the issue number, and assignees: ["<current-user-login>"] (the login obtained in step "Get current user").ado/wit_update_work_item to set the System.AssignedTo field to the current user.If the assignment call fails (permission error, user lookup empty, API error), STOP and report the failure rather than silently proceeding to later checks. The downstream flow (state update, branch creation, PR linkage) assumes the work item is owned by the current user.
status:in-progressboard-config skill for details)This task has unfinished dependencies:
- #[ID]: [title] (state: [state])
[V] View dependency details
[O] Work on another task
[I] Ignore and continue anyway (not recommended)
There are higher priority tasks available:
- #[ID]: [title] (P1)
Requested task: #[ID] (P2)
[P] Pick the higher priority task (recommended)
[C] Continue with the requested task
You already have [N] tasks in progress:
- #[ID]: [title]
[F] Finish a task before picking up another (recommended)
[C] Continue and pick up another task
docs/features/ directory. If the user specified a feature, use it.Developers should work on only one task at a time. Work happens at the task level, not at the feature, user story, or epic level directly.
When synchronizing with the board, the agent should:
feature:<name>, type:user-story, type:task…
Systematically triage failures and fix broken builds or unexpected runtime issues.
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.
Standardize formatting and writing style for project Markdown documentation.
Create well-structured issues, stories, tasks, epics, and features on boards.
Suggests the most suitable next implementation task after finishing current work.
Triages issues with label-driven state transitions and durable, resumable records.
Coordinate GitHub and Linear workflows for triage, tracking, and execution alignment.
Create and maintain ADRs with checks, references, and planning support.
Sync active tasks and refresh project memory to catch missed work.