When the work item has no assignee, do not skip this step. Execute the assignment before moving to the State update check:

• GitHub: Call github/issue_write with method: "update", the issue number, and assignees: ["<current-user-login>"] (the login obtained in step "Get current user").
• Azure DevOps: Call 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.

2. State update

• Move the task to active state:
  • GitHub: Add label status:in-progress
  • Azure DevOps: Change State per process template (invoke board-config skill for details)
• Check the parent User Story:
  • If the parent US is not in progress, update it as well
  • Inform: "User Story #[ID] moved to In Progress."

3. Dependency check

• GitHub: Look for "Depends on: #NNN" in the body
• Azure DevOps: Look for links of type "Predecessor"
• For each unfinished dependency (open issue / state != Done|Closed):

  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)
  

4. Priority check

• Search for available tasks (no assignee, same feature)
• If there are tasks with higher priority available:

  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
  

5. Capacity check

• Search for in-progress tasks assigned to the current user
• If the user already has 3 or more tasks in progress:

  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
  

tasks.md (when no issue/work item is mentioned)

1. Identify the current feature by checking the docs/features/ directory. If the user specified a feature, use it.
2. Read tasks.md for the task list and execution plan
3. Proceed with the implementation flow

Main Execution Rule

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.

Board Synchronization

When synchronizing with the board, the agent should:

1. List ALL issues/work items in the repository/project
2. Identify feature-related issues using multiple strategies:
   • By label/tag: feature:<name>, type:user-story, type:task
   • By title: contains the feature name or keywords

…

git-branch

帮助你创建、切换并检查代码分支，确保实现前遵循正确分支策略。

triage-workflow

用标签驱动的问题分诊流程，规范状态流转并生成可追溯分诊记录。