Claude Code CommandOrchestration17 installs

Feature Pipeline

Execute implementation tasks from a design document. Tasks are tracked as markdown checkboxes directly in the design file.

Install with the Claude Code Templates CLI
$ npx claude-code-templates@latest --command="orchestration/feature-pipeline" --yes

Requires Claude Code. The command adds this command to your project's .claudedirectory — nothing runs on ToolZip's servers.

What's inside this command

Component source

Feature Pipeline

Execute implementation tasks from a design document using markdown checkboxes.

Input Detection

$ARGUMENTS should be a path to a design markdown file (e.g., docs/designs/xxx.md)

If empty or unclear, ask user for the design file path.

Phase 1: Initialize

  • Read the design file
  • Run python3 .claude/skills/task-execution-engine/scripts/task_manager.py status --file <design.md> to show current progress
  • If all tasks completed, report and exit
  • Otherwise, proceed to execution

Phase 2: Execution Loop

UNATTENDED MODE - No questions, no stopping
LOOP:
  1. RUN: task_manager.py next --file <design.md> --json
  2. IF no task available → EXIT to Phase 3
  3. READ task details (files, criteria)
  4. IMPLEMENT the task
     - Create/modify files as specified
     - Follow codebase patterns
     - Run tests if applicable
  5. VERIFY acceptance criteria
  6. UPDATE status:
     - Success: task_manager.py done --file <design.md> --task "Title"
     - Failure: task_manager.py fail --file <design.md> --task "Title" --reason "..."
  7. OUTPUT result summary
  8. CONTINUE (go to step 1)

Phase 3: Completion

  • Run task_manager.py status --file <design.md> to show final summary
  • Report:
- Tasks completed

- Tasks failed (with reasons)

- Files modified

  • Ask if user wants to commit changes to git

Implementation Guidelines

For Each Task:

  • Read files specified in task's files: line
  • Understand criteria from the checkbox items
  • Implement following existing codebase patterns
  • Verify each acceptance criterion is met
  • Update the design file with completion status

Decision Making:

  • If unclear about implementation details → use codebase patterns
  • If blocked by missing dependency → mark as failed, continue
  • If needs external resource → mark as failed with reason, continue

Status Updates:

# Mark task completed (updates checkbox to [x] ✅)
python3 .claude/skills/task-execution-engine/scripts/task_manager.py done \
  --file <design.md> --task "Task Title"

# Mark task failed (updates checkbox to [x] ❌ with reason)
python3 .claude/skills/task-execution-engine/scripts/task_manager.py fail \
  --file <design.md> --task "Task Title" --reason "Error description"

Output Format

After each task:

---TASK RESULT---
task: Task Title
status: completed|failed
files: [list of modified files]
notes: Brief description
---END TASK RESULT---

Error Handling

ErrorAction
Task implementation failsMark failed, continue to next
Script errorLog error, retry once, then fail task
No tasks availableExit loop, show summary
File not foundAsk user for correct path

Key Rules

  • NEVER stop in the middle of execution loop
  • NEVER ask questions during execution
  • ALWAYS update task status in design file
  • Exit only when no pending tasks remain
Type
Command
Category
Orchestration
Installs
17
Source
GitHub ↗

Related Claude Code Commands

Catalog data and component content are sourced from the open-source davila7/claude-code-templates project (MIT license). ToolZip curates the listing and writes original descriptions; every component links back to its original source. Claude Code is a product of Anthropic. ToolZip is an independent catalog and is not affiliated with or endorsed by Anthropic.