workflow-backend

Coordinate backend-agnostic workflow orchestration across issues, specs, and tasks.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/matlockx/track-work --skill workflow-backend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-backend
Source: https://github.com/matlockx/track-work/tree/main/.agent/skills/workflow-backend
Command: npx skills add https://github.com/matlockx/track-work --skill workflow-backend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reference for backend-agnostic workflow orchestration in OpenCode. Use this skill when commands or agents need to reason about issues, specs, implementation tasks, phase progression, dependency readiness, or workflow state transitions through the configured backend interface.

Core Features & Use Cases

  • Provides a unified interface to manage Issue, Spec, and Task lifecycles across different backends.
  • Enforces standard lifecycle transitions (draft/approved for specs; todo/inprogress/review/done for tasks) and guides orchestration via backend APIs.
  • Enables safe, backend-agnostic decision making for workflow state changes with validation and error handling.

Quick Start

Describe a typical flow: fetch the issue, create or fetch its spec, and create tasks once the spec is approved, via the configured backend interface.

Frequently Asked Questions about workflow-backend

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

FAQPage Schema
How do I manage issue and task lifecycles across different backend interfaces?

Backend-agnostic workflow orchestration manages issue and task lifecycles across different backend interfaces by enforcing standard state transitions like todo, inprogress, review, and done through a unified API with validation.

What is the standard workflow for moving specs to implementation tasks?

The standard workflow for moving specs to implementation tasks involves fetching an issue, creating or fetching its spec, and creating tasks once the spec is approved, guiding progression through the configured backend interface.

How do AI agents reason about workflow state transitions safely?

AI agents reason about workflow state transitions safely by applying backend-agnostic lifecycle rules and validation logic, ensuring safe decision making for spec and task management changes through the configured backend interface.

Can I use workflow orchestration without being tied to a specific issue tracking backend?

Yes, you can use backend-agnostic workflow orchestration without being tied to a specific issue tracking backend, as it provides a unified interface to manage lifecycles and guides orchestration via backend APIs without hard dependencies.

What validation logic is enforced during spec and task state progression?

Validation logic enforced during spec and task state progression includes standard lifecycle transitions, such as draft to approved for specs and todo to done for tasks, ensuring dependency readiness and safe workflow state changes.