work

Manage work items with blocks dependencies, ULID IDs, and JSON output.

9|3|Updated Jun 29, 2012
One-click install
npx skills add https://github.com/whilp/dotfiles --skill work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work
Source: https://github.com/whilp/dotfiles/tree/main/.claude/skills/work
Command: npx skills add https://github.com/whilp/dotfiles --skill work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill centralizes work items as Lua files with a dependency model, enabling reliable task sequencing and progress tracking.

Core Features & Use Cases

  • Dependency-aware scheduling: blocks/blocked relationships control execution order.
  • ULID-based IDs: time-ordered, globally unique IDs for traceability.
  • Output readiness: JSON-ready outputs for automation and reporting.

Quick Start

Create a new Work item with bin/work add "task title" and optionally add dependencies with blocks=....

Frequently Asked Questions about work

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

FAQPage Schema
How do I manage work tasks with dependencies?

Work tasks with dependencies are managed by creating items with the blocks field to define which tasks block or are blocked by others. Use `bin/work add` to create tasks, set dependencies via blocks relationships, and track execution order through the dependency model for reliable task sequencing.

How do I create and track work items with due dates?

Create work items using `bin/work add` with optional absolute or relative due dates. The system computes transitive due dates based on dependencies, automatically determining when blocked tasks become available and tracking progress through tree, show, and log views.

What's the best way to organize and visualize task dependencies?

Task dependencies are visualized using the tree view to see hierarchical relationships defined by blocks fields. Use show and log views to inspect individual items and their dependency history, leveraging ULID-based time-ordered identifiers for traceability across all tasks.

Can I export work tasks and dependency data as JSON?

Yes, all work commands—add, list, tree, and show—output JSON-enabled results for automation and reporting. This enables programmatic access to tasks, dependencies, and due dates for integration with external systems or custom analysis workflows.

Do I need prior setup to start tracking work items?

No complex setup is required. Work items are stored as Lua files under ~/*/*/work, and you begin immediately with `bin/work add`. The system handles ULID generation and dependency tracking automatically without external configuration.