Task Workflow

Create, update, and list tasks with status transitions and blocking relationships.

19|5|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/lukacf/meerkat --skill task-workflow-lukacf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Task Workflow
Source: https://github.com/lukacf/meerkat/tree/main/meerkat-tools/skills/task-workflow
Command: npx skills add https://github.com/lukacf/meerkat --skill task-workflow-lukacf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Task Workflow solves the problem of keeping work organized across multiple tasks by providing a clear pattern for creating, updating, and listing tasks, with defined status transitions and blocking relationships.

Core Features & Use Cases

  • Creating Tasks: Use task_create with a clear subject and description:
    • Subject should be imperative ("Fix login bug", "Add API endpoint")
    • Description should include acceptance criteria
  • Status Transitions: Tasks flow through: pending -> in_progress -> completed
    • Set in_progress when you start working on a task
    • Set completed only when fully done
    • Use deleted to remove irrelevant tasks
  • Blocking Relationships: Use addBlocks and addBlockedBy to express dependencies:
    • A task with blockedBy cannot be started until dependencies complete
    • Check TaskList to find unblocked tasks
  • Best Practices:
    • Create tasks before starting work to track progress
    • Update status as you work
    • Use TaskList after completing a task to find the next one
    • Prefer working on tasks in ID order (lowest first)

Quick Start

Create a task with a clear subject and description, then update its status through pending, in_progress, and completed.

Frequently Asked Questions about Task Workflow

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

FAQPage Schema
How do I manage task dependencies and blocking relationships in a project workflow?

Task dependencies are managed using addBlocks and addBlockedBy relationships to express blocking tasks. A task with blockedBy cannot transition to in_progress until its dependencies complete, ensuring clear task lifecycles and proper execution order across the project.

What are the standard status transitions for project management tasks?

Standard status transitions for project management tasks flow from pending to in_progress to completed. You set in_progress when starting work, completed when fully done, and deleted to remove irrelevant tasks, maintaining clear task lifecycles throughout the workflow.

How do I create tasks with proper subject lines and descriptions?

Create tasks using task_create with an imperative subject line like 'Fix login bug' or 'Add API endpoint' and a description containing acceptance criteria. This structure organizes work by ensuring tasks have clear, actionable goals before status transitions begin.

How do I find the next unblocked task to work on after completing a current one?

Use TaskList after completing a task to find the next unblocked task. Check the list for tasks without active blockedBy relationships, then prefer working on tasks in ID order starting with the lowest number to maintain consistent workflow progression.

Can I use task workflows for both individual contributors and project teams?

Task workflows apply to both project teams and individual contributors who need clear task lifecycles. The system structures work with create, update, and list operations that handle status transitions and blocking relationships across multiple tasks for any scale.

When should I use deleted status versus completed for task management?

Use completed status when a task is fully done and its acceptance criteria are met, while deleted removes irrelevant tasks from the workflow. Both are valid status transitions from in_progress, but deleted prevents unnecessary work from cluttering your TaskList.