Run any Skill in Manus with one click

ticket

Stars2

Forks1

UpdatedMay 18, 2026 at 07:05

Transition Azure DevOps work item state. Trigger when user says "ticket <id> active", "set ticket cr", "/df:ticket", or wants to move a work item between states (active, code-review, ready, closed).

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

lttr

lttr/claude-marketplace

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	ticket
description	Transition Azure DevOps work item state. Trigger when user says "ticket <id> active", "set ticket cr", "/df:ticket", or wants to move a work item between states (active, code-review, ready, closed).

Ticket

Update Azure DevOps work item state via az boards work-item update.

Input Format

$ARGUMENTS = <id> <state>.

Synonym	Azure DevOps state
`active`, `start`, `in-progress`	`Active`
`cr`, `code-review`, `review`	`Code Review`
`ready`, `done-dev`	`Ready`
`closed`, `done`, `complete`	`Closed`

Unknown state → ask user. Missing id → ask. Missing state → ask.

Workflow

1. Parse + map state

Extract id (numeric) and state synonym. Map to canonical Azure DevOps state.

2. Update

az boards work-item update --id <id> --state "<State>"

3. Confirm

Print: work item id, title, new state.

Notes

States above match the most common Azure DevOps process templates. If your project uses different state names (e.g. Doing, In Review), pass the exact label.
Branch creation lives in the feature-branch skill — keeps state changes orthogonal.

More from this repository

same repository

changelog

lttr/claude-marketplace

Show recent Claude Code changes personalized to user's setup. Trigger when user asks about changelog, "what's new", "cc changelog", "claude code updates", "recent changes", or wants to know what changed in Claude Code.

2026-07-232

handoff

lttr/claude-marketplace

Write ~/.claude/custom-handoff.md to hand off current work to the next session

2026-07-232

list-builtin-tools

lttr/claude-marketplace

List all built-in Claude Code tools

2026-07-232

list-hooks

lttr/claude-marketplace

List all configured hooks

2026-07-232

tdd

lttr/claude-marketplace

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

2026-07-232

grill-with-docs

lttr/claude-marketplace

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (GLOSSARY.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

2026-07-232

name	ticket
description	Transition Azure DevOps work item state. Trigger when user says "ticket <id> active", "set ticket cr", "/df:ticket", or wants to move a work item between states (active, code-review, ready, closed).

Ticket

Update Azure DevOps work item state via az boards work-item update.

Input Format

$ARGUMENTS = <id> <state>.

Synonym	Azure DevOps state
`active`, `start`, `in-progress`	`Active`
`cr`, `code-review`, `review`	`Code Review`
`ready`, `done-dev`	`Ready`
`closed`, `done`, `complete`	`Closed`

Unknown state → ask user. Missing id → ask. Missing state → ask.

Workflow

1. Parse + map state

Extract id (numeric) and state synonym. Map to canonical Azure DevOps state.

2. Update

az boards work-item update --id <id> --state "<State>"

3. Confirm

Print: work item id, title, new state.

Notes

States above match the most common Azure DevOps process templates. If your project uses different state names (e.g. Doing, In Review), pass the exact label.
Branch creation lives in the feature-branch skill — keeps state changes orthogonal.