work-on

Manages GitHub and Azure DevOps tasks and Pull Requests through a two-phase approval workflow.

2|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/gautam-achieveai/ClaudePlugins --skill work-on-gautam-achieveai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-on
Source: https://github.com/gautam-achieveai/ClaudePlugins/tree/main/development/skills/work-on
Command: npx skills add https://github.com/gautam-achieveai/ClaudePlugins --skill work-on-gautam-achieveai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github, azure-devops, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The work-on Skill solves the problem of managing tasks and Pull Requests in software development. It provides an autonomous, two-phase workflow to plan, implement, and verify code changes, ensuring a structured and safe development process.

Core Features & Use Cases

  • Autonomous Workflow: Plans and executes development tasks with explicit approval and feedback loops.
  • Provider-Agnostic: Works with GitHub and Azure DevOps, allowing for a unified approach across different platforms.
  • Task and PR Management: Streamlines the creation, review, and completion of tasks and Pull Requests.
  • Use Case: With the work-on Skill, a developer can initiate a new task, plan the implementation, and get explicit approval before proceeding with the actual code changes.

Quick Start

To start a new task, run: /work-on <task_id>

Frequently Asked Questions about work-on

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate task and PR management across GitHub and Azure DevOps?

Autonomous task and PR management across GitHub and Azure DevOps is handled through a provider-agnostic workflow that plans, implements, and verifies code changes. It requires the respective platform APIs for integration, ensuring structured development with explicit approval and feedback.

What is an autonomous development workflow for Pull Requests?

An autonomous development workflow for Pull Requests is a two-phase process that plans and executes code changes with explicit approval and feedback loops. It streamlines PR creation, review, and completion to ensure a safe, structured development process.

Can I use a single tool for developer workflow automation on both GitHub and Azure DevOps?

Yes, a provider-agnostic autonomous workflow supports developer workflow automation on both GitHub and Azure DevOps. It unifies task and PR management across platforms, allowing structured planning, implementation, and verification using their respective APIs.

How do I start a new development task with autonomous planning and approval?

To start a new development task with autonomous planning and approval, you run the task command with the specific task ID. The workflow then initiates a two-phase process to plan the implementation and await explicit approval before proceeding with code changes.

Does autonomous PR management require explicit approval before implementing code changes?

Yes, autonomous PR management requires explicit approval before implementing code changes. The two-phase workflow ensures structured development by separating planning from implementation, incorporating feedback loops to verify changes safely.

What are the limitations of using a provider-agnostic workflow for task management?

The primary limitation of this provider-agnostic task management workflow is its dependency on having the GitHub API or Azure DevOps API configured for integration, as it requires these platforms to handle task and PR creation, planning, and verification.