dev-workflow-orchestrator

dundas's avatarfrom dundas

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

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 9, 2025⬇️1downloads
[Project Management]

When & Why to Use This Skill

The Dev-Workflow Orchestrator is a comprehensive Claude skill designed to streamline the software development lifecycle by automating the transition from product requirements to executable tasks. It manages the end-to-end process of PRD creation, hierarchical task generation, and step-by-step task processing, incorporating mandatory user confirmation gates to ensure accuracy and alignment at every stage.

Use Cases

  • Feature Kickoff: Transform a high-level feature request into a structured PRD and a detailed technical roadmap automatically while ensuring all requirements are clarified.
  • Controlled Implementation: Execute complex coding tasks with a 'gated' approach, allowing developers to review and approve sub-tasks before the AI proceeds to the next step.
  • Task Decomposition: Automatically break down large project goals into manageable parent and sub-tasks with associated testing notes and file references to maintain organized project structure.
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.