Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
craigspaterson avatar

Start Story

  • 1 installs
  • 1 repo stars
  • Updated July 5, 2026
  • craigspaterson/agent-skills

Initiate user stories and tasks in project management systems.

About

Agent skill for creating and starting user stories in agile workflows. Bridges agent tools and project tracking for seamless work initiation.

  • User story creation and initiation
  • Agile workflow integration

Start Story by the numbers

  • 1 all-time installs (skills.sh)
  • Ranked #2,479 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Data as of Jul 8, 2026 (Skillselion catalog sync)
npx skills add https://github.com/craigspaterson/agent-skills --skill start-story

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1
repo stars1
Last updatedJuly 5, 2026
Repositorycraigspaterson/agent-skills

What it does

Initiate user stories and tasks in project management systems.

Files

SKILL.mdMarkdownGitHub ↗

Start Story

Activates an ADO work item and creates the feature branch in one step.

Prerequisites

Ensure these are set in ~/.claude/settings.json under the env block:

{
  "env": {
    "ADO_ORG": "your-org",
    "ADO_PROJECT": "your-project",
    "ADO_USER": "you@example.com"
  }
}

ADO_USER is the email address used to assign the work item. The script skips the assignment update if the work item is already assigned to that user.

Step 1 — Parse the work item ID

Extract the numeric ID from the user's input. Accept any of these formats:

  • AB#38
  • AB38
  • 38

Strip any AB# or AB prefix to get the numeric ID.

Step 2 — Call the script

pwsh ~/.claude/skills/start-story/scripts/start-story.ps1 -Id {N}

Replace {N} with the numeric work item ID (e.g. 38, not AB#38 — the script handles the prefix internally but passing the number is cleanest).

Pass -Org, -Project, or -User only if the user explicitly overrides them; otherwise the script reads from env vars.

Step 3 — Report result

After the script completes, tell the user:

  • Whether the work item state was changed to Active (or was already Active)
  • Whether the assignee was updated (or was already correct)
  • The feature branch name that was created and pushed

If the script errors, surface the full error message and do not retry silently.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.