backlog

Define a standard backlog interface with operations and sync hooks.

12|1|Updated Feb 13, 2026

Search Tags:#workflow #agile #backlog #operations #interface #project-management #backends

Ready to run

npx skills add https://github.com/ovargas/virtual-team --skill backlog-ovargas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: backlog
Source: https://github.com/ovargas/virtual-team/tree/main/skills/backlog
Command: npx skills add https://github.com/ovargas/virtual-team --skill backlog-ovargas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

backlog defines a standard interface for backlog management so commands can interact with any active implementation (local or external) without caring about formatting details.

Core Features & Use Cases

Define operations: list, get, get_feature_progress, next_id, create, start, mark_implemented, complete.
Support local and external backends via stack-based selection and optional sync hooks.
Ensure consistent status transitions and spec linkage across features.

Quick Start

Load the backlog skill and begin performing operations through the active implementation (local or external).

Frequently Asked Questions about backlog

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

FAQPage Schema

What is a unified backlog interface for project management?▼

A unified backlog interface standardizes backlog operations—list, get, create, start, complete, and progress—across both local and external backends, ensuring predictable behavior without worrying about formatting details.

How do I manage agile backlog operations across multiple backends?▼

Manage agile backlog operations across backends by loading a standard skill that defines required operation names, status transitions, and sync hooks (push/pull) to interact with any active local or external implementation.

Does this backlog skill support external backends and sync hooks?▼

Yes, the backlog skill supports external backends via stack-based selection and optional sync hooks for push and pull operations, enabling integration with external services and consistent status transitions.

Can I use local and external backlog backends interchangeably with this workflow?▼

Yes, local and external backlog backends are interchangeable because the skill enforces a standard interface that adapts operations like list, create, start, and complete to the active backend seamlessly.

What are the required operations for a standard backlog management interface?▼

Required operations for a standard backlog management interface include list, get, get_feature_progress, next_id, create, start, mark_implemented, and complete, ensuring consistent status transitions and spec linkage.

Why does my backlog workflow break when switching between project-management backends?▼

Backlog workflows break when switching backends due to inconsistent operation names and status transitions; enforcing a standard backlog contract with sync hooks prevents integration failures and ensures predictable behavior.