Files
claude-task-master/.claude/commands/tm/workflows/pipeline.md
neno b9299c5af0 feat: Claude Code slash commands for Task Master (#774)
* Fix Cursor deeplink installation with copy-paste instructions (#723)

* fix: expand-task (#755)

* docs: Update o3 model price (#751)

* docs: Auto-update and format models.md

* docs: Auto-update and format models.md

* feat: Add Claude Code task master commands

Adds Task Master slash commands for Claude Code under /project:tm/ namespace

---------

Co-authored-by: Joe Danziger <joe@ticc.net>
Co-authored-by: Ralph Khreish <35776126+Crunchyman-ralph@users.noreply.github.com>
Co-authored-by: Volodymyr Zahorniak <7808206+zahorniak@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: neno-is-ooo <204701868+neno-is-ooo@users.noreply.github.com>
2025-06-21 20:48:20 +02:00

1.6 KiB

Execute a pipeline of commands based on a specification.

Arguments: $ARGUMENTS

Command Pipeline Execution

Parse pipeline specification from arguments. Supported formats:

Simple Pipeline

init → expand-all → sprint-plan

Conditional Pipeline

status → if:pending>10 → sprint-plan → else → next

Iterative Pipeline

for:pending-tasks → expand → complexity-check

Smart Pipeline Patterns

1. Project Setup Pipeline

init [prd] → 
expand-all → 
complexity-report → 
sprint-plan → 
show first-sprint

2. Daily Work Pipeline

standup →
if:in-progress → continue →
else → next → start

3. Task Completion Pipeline

complete [id] →
git-commit →
if:blocked-tasks-freed → show-freed →
next

4. Quality Check Pipeline

list in-progress →
for:each → check-idle-time →
if:idle>1day → prompt-update

Pipeline Features

Variables

  • Store results: status → $count=pending-count
  • Use in conditions: if:$count>10
  • Pass between commands: expand $high-priority-tasks

Error Handling

  • On failure: try:complete → catch:show-blockers
  • Skip on error: optional:test-run
  • Retry logic: retry:3:commit

Parallel Execution

  • Parallel branches: [analyze | test | lint]
  • Join results: parallel → join:report

Execution Flow

  1. Parse pipeline specification
  2. Validate command sequence
  3. Execute with state passing
  4. Handle conditions and loops
  5. Aggregate results
  6. Show summary

This enables complex workflows like: parse-prd → expand-all → filter:complex>70 → assign:senior → sprint-plan:weighted