Transition Azure DevOps work item state. Trigger when user says "ticket <id> active", "set ticket cr", "/dev-azdo:ticket", or wants to move a work item between states (active, code-review, ready, closed).
Scanned 9/3/2026
Install to Claude Code
Skills Directorynpx -y skills add lttr/claude-marketplace --skill ticket --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Ticket?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/lttr-ticket)More formats (shields.io, HTML) on the badges page.
---
name: ticket
description: Transition Azure DevOps work item state. Trigger when user says "ticket <id> active", "set ticket cr", "/dev-azdo: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
```bash
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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
