What is ado-create-story?

An interactive workflow for creating an Azure DevOps User Story under an existing Feature. A User Story describes a specific need or function, while a Feature is a larger capability that groups related stories.

Use it when you need to gather requirements and create a properly structured User Story as a child of an existing Feature.

It guides the required questions and applies the project’s Azure DevOps conventions. It also prevents command-line text from bypassing the intended interactive requirements process.

ado-create-story — Skill by charlesjones-dev

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/charlesjones-dev/claude-code-plugins-dev/ado-create-story

Any agent

npx skills add charlesjones-dev/claude-code-plugins-dev --skill ado-create-story

Clone the repo

git clone --depth 1 https://github.com/charlesjones-dev/claude-code-plugins-dev

Made for: Claude Code, Codex.

Or install ai-ado, the plugin that ships this one along with the rest of its 7 skills.

Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,423 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00025	$0.03423
Opus 5	$0.00013	$0.01711
Sonnet 5	$0.00005	$0.00685
Haiku 4.5	$0.00003	$0.00342

Measured 3d ago against content hash 609b26be4414, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ado-create-story scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/ai-ado/skills/ado-create-story/SKILL.md · 366 lines

How it starts

The opening of the file, as written. The whole thing — 366 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Azure DevOps User Story

Interactively create a new User Story work item as a child of an existing Feature in Azure DevOps using the organization's configured conventions and guidelines.

Instructions

CRITICAL: This command MUST NOT accept any arguments. If the user provided any text, story titles, descriptions, IDs, or other arguments after this command (e.g., /ado-create-story "My Story" or /ado-create-story 123), you MUST COMPLETELY IGNORE them. Do NOT use any story titles, descriptions, IDs, or other arguments that appear in the user's message. You MUST ONLY gather requirements through the interactive prompts as specified below.

BEFORE DOING ANYTHING ELSE: Validate Azure DevOps configuration in CLAUDE.md, then begin gathering user story information. DO NOT skip these steps even if the user provided arguments after the command.

This command creates a User Story work item following the organization's Azure DevOps conventions defined in CLAUDE.md.

Phase 1: Validate Azure DevOps Configuration

Before proceeding with user story creation, verify that Azure DevOps configuration exists:

Use the Read tool to read CLAUDE.md from the project root

If the file doesn't exist OR doesn't contain an "## Azure DevOps" section:

Display the following error message:

❌ Azure DevOps configuration not found

CLAUDE.md does not contain Azure DevOps configuration.

Please run /ado-init first to configure Azure DevOps settings for this project.

The /ado-init command will:
- Configure your organization, project, and team
- Set up Area Path and Iteration Path defaults
- Define naming conventions and work item guidelines
- Optionally configure the Azure DevOps MCP server

STOP and do not proceed further

If Azure DevOps section exists:
- Parse the CLAUDE.md content to extract configuration values:
  - Organization name (look for text after 'specify the organization as "')
  - Project name (look for text after 'the project as "')
  - Team name (look for text after 'the team as "')
  - Area Path (look for text after 'Area Path" set to "')
  - Iteration Path (look for text after 'Iteration Path" set to "')
  - Naming convention preference (check if decimal notation is used)
- Store these values for use in story creation
- Proceed to Phase 2

Read the full file on GitHub · 366 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago First seen · 366 lines · 25 tokens per session scan A 609b26be4414

Subscribe to this mod's changes

ado-create-story is a skill published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (34 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 3,423 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Project management ai claude claude-code developer-tools git-tools

gwm

Manage git worktrees across any repository with the gwm Rust binary (CLI + ratatui TUI). Use when the user asks to create / list / remove / bootstrap / switch / link worktrees, run a command across worktrees (gwm exec) or reclaim build artifacts (gwm clean), materialise a PR into a worktree (gwm review), drive a…

kbrdn1/gwm-cli · 379 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens