task

Task Management Command

Create, update, and manage structured development tasks using Beads for fast, scalable tracking. This command is a wrapper around bd commands with EdgarTools-specific conventions.

Tracking System: Beads (bd commands) Documentation: ROADMAP.md (strategic planning), VELOCITY-TRACKING.md (historical analysis) Integration: Coordinates with product-manager for prioritization

Usage Examples

# Create a new feature task
/task new feature "Multi-company financial comparison"

# Create a bug fix task from GitHub issue
/task new bug "Cash flow statement missing values" --github=408

# List active tasks
/task list

# Show task details
/task show edgartools-abc

# Mark task as complete
/task complete edgartools-abc

Note: This command is a convenience wrapper around bd commands. For direct Beads usage:

bd create --title "Feature: X" --status open --priority P1 --labels feature
bd list --status open
bd update ISSUE_ID --status in_progress
bd update ISSUE_ID --status done

Command Implementation

This command wraps bd (Beads) commands with EdgarTools conventions:

Creating New Tasks

# Map task type to labels
case $task_type in
    feature) labels="feature" ;;
    bug) labels="bug" ;;
    research) labels="research" ;;
    refactor) labels="refactor" ;;
esac

# Create in Beads with external ref if from GitHub
if [ -n "$github_issue" ]; then
    bd create --title "$task_type: $task_title" \
              --status open \
              --external-ref "gh:$github_issue" \
              --labels "$labels" \
              --priority P2
else
    bd create --title "$task_type: $task_title" \
              --status open \
              --labels "$labels" \
              --priority P2
fi

# Optionally create detailed plan markdown file for complex tasks
# (Only create if task requires architectural planning or multiple steps)

Listing Tasks

# List all open tasks
bd list --status open

# Or filter by type
bd list --status open --labels feature
bd list --status open --labels bug