@chris1807/claude-kit 2.1.11 → 2.1.13

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@chris1807/claude-kit",
-  "version": "2.1.11",
+  "version": "2.1.13",
   "description": "Claude Code starter kit for Azure DevOps teams — agents, hooks, MCP servers, slash commands, and end-to-end work item → PR → release → deploy workflow automation",
   "type": "module",
   "bin": {

package/templates/agents/global/backend.md

@@ -2,7 +2,7 @@
 name: backend
 description: Writes .NET 10/C# backend code following Clean Architecture across Domain, Application, Infrastructure, and API layers. Handles controllers, services, interfaces, DTOs, and repositories (MongoDB + SQL Server).
 tools: Read, Write, Edit, Glob, Grep, Bash
-model: opus
+model: claude-opus-4-8
 ---
 
 # Backend Developer

package/templates/agents/global/frontend.md

@@ -2,7 +2,7 @@
 name: frontend
 description: Writes React/TypeScript frontend code with MUI 6, Redux Toolkit, React Hook Form, and TanStack Query. Implements UI matching the HTML mockups.
 tools: Read, Write, Edit, Glob, Grep, Bash
-model: opus
+model: claude-opus-4-8
 ---
 
 # Frontend Developer

package/templates/agents/global/manager.md

@@ -2,7 +2,7 @@
 name: manager
 description: Orchestrates the development workflow. Breaks down features, delegates to specialized agents, and enforces the Phase/Feature/Test/UAT workflow.
 tools: Task, Read, Write, Edit, Glob, Grep, Bash
-model: opus
+model: claude-opus-4-8
 ---
 
 # Team Manager

package/templates/agents/global/mockup.md

@@ -2,7 +2,7 @@
 name: mockup
 description: Creates and updates HTML mockup files for new features. Maintains the design system and generates screen designs before implementation begins.
 tools: Read, Write, Edit, Glob, Grep
-model: opus
+model: claude-opus-4-8
 ---
 
 # Mockup Designer

package/templates/commands/plan-backlog.md

@@ -182,6 +182,7 @@ For each approved task, call `mcp__azure-devops__wit_create_work_item` with:
   - `Microsoft.VSTS.Scheduling.RemainingWork` — the same hour estimate
   - `System.IterationPath` — copy from the parent (which is the root)
   - `System.AreaPath` — copy from the parent
+  - `System.AssignedTo` — copy from the parent (pass the parent's `uniqueName` / email if its `System.AssignedTo` value is an identity object). If the parent is unassigned, leave this field unset rather than failing.
 
 Then link the new task as a child of the parent with `mcp__azure-devops__wit_add_child_work_items` (or fall back to `wit_work_items_link` with link type `System.LinkTypes.Hierarchy-Forward` from parent → task).
 

package/templates/commands/rework.md

@@ -149,6 +149,7 @@ If the user provided hours (suggested or overridden):
      - `Microsoft.VSTS.Scheduling.RemainingWork` — the agreed hours
      - `System.AreaPath` — same as the parent
      - `System.IterationPath` — same as the parent
+     - `System.AssignedTo` — same as the parent (copy the parent's `System.AssignedTo` value; pass the `uniqueName` / email if the parent's value is an identity object). If the parent is unassigned, leave this field unset rather than failing.
 
 2. Link the new Task as a child of the parent work item via `wit_work_items_link`:
    - **type**: `Child` (the parent → child link from the parent's perspective; equivalent to `Parent` from the task's perspective)