dev-workflow-orchestrator

Orchestrate PRD creation, task generation, and gated task processing with user confirmations between phases.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 5, 2026

When & Why to Use This Skill

The Development Workflow Orchestrator is a sophisticated Claude skill designed to automate and manage the end-to-end software development lifecycle (SDLC). It bridges the gap between high-level product requirements and technical execution by orchestrating PRD creation, hierarchical task generation, and gated task processing. By implementing a 'human-in-the-loop' interaction model with mandatory confirmation gates, it ensures high-precision project tracking and prevents AI drift during complex development cycles.

Use Cases

  • End-to-End Feature Launch: Transform a vague feature idea into a structured Product Requirements Document (PRD) and a fully executable task list with automated progress tracking.
  • Agile Task Decomposition: Automatically break down complex technical requirements into manageable parent and sub-tasks, allowing developers to review and approve the logic before implementation begins.
  • Controlled Code Implementation: Execute development sprints with step-by-step verification, ensuring each sub-task passes testing and commit protocols before moving to the next phase.
  • Project Standardization: Maintain consistent documentation and task structures across a repository by using standardized templates for PRDs and task lists.
namedev-workflow-orchestrator
descriptionOrchestrate PRD creation, task generation, and gated task processing with user confirmations between phases.

Development Workflow Orchestrator

Overview

Coordinates the end-to-end workflow: create PRD → generate tasks → process tasks with gated confirmations.

Steps

  1. PRD Creation (uses prd-writer)
    • Ask clarifying questions.
    • Produce PRD and save to /tasks/[n]-prd-[feature].md.
  2. Task Generation (uses tasklist-generator)
    • Read the PRD.
    • Generate parent tasks only; present and pause for "Go".
    • After "Go", generate sub-tasks, relevant files, and testing notes.
    • Save to /tasks/tasks-[prd-file-name].md.
  3. Task Processing (uses task-processor)
    • Work one sub-task at a time with explicit pauses.
    • Follow test/commit protocol for completed parent tasks.
    • Keep "Relevant Files" accurate.

Interaction Model

  • Phase gates:
    • Between PRD and tasks.
    • Between parent tasks and sub-tasks (requires "Go").
    • Between sub-tasks (requires "yes"/"y").

References

  • See reference.md.