Feature Pipeline
Execute implementation tasks from a design document. Tasks are tracked as markdown checkboxes directly in the design file.
npx claude-code-templates@latest --command orchestration/feature-pipeline Scanned by NVIDIA SkillSpector
Automated static analysis (no LLM) · v2.12.0 · 2026-10-17
Partial analysis: some checks could not run on this component.
SkillSpector looks for patterns such as shell commands, credential access, network calls or unpinned dependencies. An observation is something worth reading in the files before you install, not a confirmed vulnerability. Components that run code locally, like hooks, MCP servers and security tooling, naturally show more of them.
No observations.
Learn more about NVIDIA SkillSpector.
Content
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
| Error | Action |
|---|---|
| Task implementation fails | Mark failed, continue to next |
| Script error | Log error, retry once, then fail task |
| No tasks available | Exit loop, show summary |
| File not found | Ask 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