ado-create-feature_skill

This skill interactively creates Azure DevOps Feature work items using configured conventions to streamline planning and tracking.

26

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill charlesjones-dev/claude-code-plugins-dev --skill ado-create-feature

  • SKILL.md10.2 KB

Overview

This skill interactively creates a new Feature work item in Azure DevOps following your organization's configured conventions. It validates the project's Azure DevOps settings, gathers feature details via guided prompts (AI-generated or manual), and creates the Feature with correct fields and HTML-formatted description.

How this skill works

First, the skill checks CLAUDE.md for an Azure DevOps configuration and extracts organization, project, team, area path, iteration path, and naming convention. It then prompts you to choose AI-assisted or manual input, collects and confirms title and description, converts the description to HTML, and calls the work item creation tool to create a Feature in the configured project. Finally, it returns a clear success message with links and next steps.

When to use it

  • You need to add a Feature to Azure DevOps that follows team conventions and defaults.
  • You want a consistent title format (decimal or descriptive) enforced automatically.
  • You prefer AI to draft professional titles and stakeholder-friendly descriptions.
  • You want the Feature created with correct Area and Iteration paths without manual copying.
  • You need a predictable workflow that produces an Azure DevOps link and next steps.

Best practices

  • Run the initialization command to configure Azure DevOps in CLAUDE.md before creating Features.
  • Choose AI mode when you have a high-level goal; provide detailed context for better results.
  • In Manual mode, follow your naming convention (e.g., '1: Feature Name' for decimal notation).
  • Keep the feature description high-level: purpose, user stories it will contain, and stakeholder value.
  • Review the generated title and description carefully and override if specifics are required.

Example use cases

  • Product manager drafts a new cross-team capability and wants a stakeholder-ready Feature created.
  • Engineering lead creates a Feature with correct Area/Iteration defaults for sprint planning.
  • PMO standardizes Feature names across projects using the team naming convention.
  • A new team member uses AI mode to craft professional titles and summaries for backlog items.

FAQ

The skill stops and instructs you to run the initialization flow to configure organization, project, team, area and iteration defaults in CLAUDE.md.

Can I provide the title or description inline with the command?

No. The command ignores any inline arguments. All values must be provided interactively via the prompts.

How is the description formatted for Azure DevOps?

The description is converted to HTML: paragraphs wrapped in <p>, line breaks as <br/>, and bullet lines become <ul>/<li> lists, then submitted as an Html-formatted field.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational