todo-workflow-design

Manage TASK-NNN task lifecycle records in Julia's todo/ directory.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/abzhaw/juliaz_agents --skill todo-workflow-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: todo-workflow-design
Source: https://github.com/abzhaw/juliaz_agents/tree/main/.agent/skills/todo-workflow-design
Command: npx skills add https://github.com/abzhaw/juliaz_agents --skill todo-workflow-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agent design and operations often require a consistent way to create, read, and update tasks within Julia's todo/ directory. This Skill standardizes task records and lifecycle states to improve traceability and collaboration.

Core Features & Use Cases

  • Standard Task Lifecycle: open → in-progress → done, with clear blockers and transitions.
  • Task Creation and Tracking: define a TASK-NNN entry with id, title, status, priority, timestamps, and notes.
  • Reading/Updating: agents can query and mutate tasks using the included conventions and inline shell examples for maintenance.
  • Use Case: An agent creates a TASK-004 for implementing streaming chat and updates its status as work progresses.

Quick Start

Create a new TASK-004 entry in the todo/ directory and begin tracking it through its lifecycle.

Frequently Asked Questions about todo-workflow-design

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

FAQPage Schema
How do I manage agent task workflows using a structured todo directory?

Agent task workflows are managed by enforcing TASK-NNN style records within a todo directory, standardizing task creation, updates, and lifecycle states from open to done for improved traceability.

What metadata is required when creating a TASK-NNN task record for automation?

Creating a TASK-NNN task record requires YAML frontmatter-based metadata, including fields for id, title, status, priority, timestamps, and notes to guide both automated agents and human operators.

How does the task lifecycle transition from open to done in agent task tracking?

The task lifecycle transitions through states like open, in-progress, and done. It enforces clear blockers and state transitions to maintain consistent task tracking across agent workflows and product planning.

Can I use shell commands to read and update task management records for agents?

Yes, agents and human operators can query and mutate tasks using included conventions and inline shell-based read and update snippets designed for maintaining task records within the todo directory.

What is the best way to structure product planning tasks for multiple agents?

The best way to structure product planning tasks is using TASK-NNN style records with standardized metadata and lifecycle states, enabling consistent creation, reading, and updating across multiple agent workflows.

Do I need YAML frontmatter to track agent tasks in a todo directory?

Yes, YAML frontmatter is required to satisfy the metadata structure for task records, ensuring that automated agents can reliably parse id, status, and priority fields within the todo directory.