work-tracker

Coordinate Amplify work items across agents using Beads backend.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/getnexar/decrypt-tool --skill work-tracker-getnexar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-tracker
Source: https://github.com/getnexar/decrypt-tool/tree/main/ai-tools/skills/work-tracker
Command: npx skills add https://github.com/getnexar/decrypt-tool --skill work-tracker-getnexar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficiently manage and coordinate work items across distributed Amplify agents by delegating backend execution to Beads, mapping Amplify concepts to Beads structures.

Core Features & Use Cases

  • Back-end integration between Amplify and Beads for work item creation, status updates, and dependency management
  • Terminology mapping: Work Item ↔ Issue, Project ↔ Epic, Status ↔ open/in_progress/closed
  • Ready-made workflows via Amplify commands and Beads CLI to create, query, update, and close items and to visualize dependencies

Quick Start

Invoke Amplify commands to create a project epic and child tasks, set dependencies, and query ready work for dispatch.

Frequently Asked Questions about work-tracker

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

FAQPage Schema
How do I track work items and dependencies across distributed Amplify agents?

To track work items across distributed Amplify agents, you delegate backend execution to Beads. The system maps Amplify concepts to Beads structures, handling epic and task creation, status updates, and dependency resolution.

What is the terminology mapping between Amplify and Beads for work item management?

The terminology mapping translates Work Item to Issue, Project to Epic, and Status to open, in_progress, or closed. This alignment allows Amplify commands to manage items within the Beads backend.

How do I visualize dependency graphs for epics and child tasks in Beads?

You visualize dependency graphs for epics and child tasks using ready-made workflows via Amplify commands and Beads CLI. These commands query ready work for dispatch and display resolved dependencies.

Does the work-tracker handle circular dependencies and non-existent items?

Yes, the work-tracker includes robust error handling for circular dependencies and non-existent items. This ensures reliable coordination and tracking of work items across distributed Amplify agents using Beads.

What is the best way to create a project epic and child tasks using Amplify and Beads?

The best way to create a project epic and child tasks is to invoke Amplify commands. These commands integrate with Beads CLI to set dependencies, update statuses, and query ready work for dispatch.