What does this skill do?

The Skill Development Pipeline Orchestrator standardizes and coordinates development tasks through a shared five-phase pipeline: Research, Planning, TDD, Review, and Commit. It automatically classifies the scope of each task (trivial, small, standard, or large) and requires two human checkpoints—plan approval and commit confirmation—to ensure that every change is reviewed and validated before being integrated into the repository.

New Features
Develop features that don't yet exist by following the entire workflow: researching libraries, planning in vertical slices, TDD, and conventional commits.
Defect Correction
Reproduce the error with a red test, apply the fix using TDD, and enable the security checker if it involves user input or authentication.
Safe Refactoring
Refactor existing code while maintaining test coverage of ≥ 80% and keeping logically grouped commits pending human approval.
Building an MVP
Turn a specification or design document into a functional MVP with guided planning and built-in safety validation.

Usage examples

✨ New feature
Add a PDF export feature for sales reports, following the entire TDD pipeline.
🐛 Fix a bug
The login form fails when special characters are entered. Investigate the issue, reproduce it using a test, and fix the bug.
♻️ Refactor module
Refactor the notifications module to use an event pattern without changing its public behavior, while maintaining test coverage.
🚀 Build an MVP
Build an MVP for a metrics dashboard based on this specification: a dashboard with sales KPIs, date filters, and CSV export.

Features

Automatic Size Classification (Right-sizing) Evaluate affected files, new dependencies, and design ambiguities to assign a level: trivial, small, standard, or large.
Five-phase pipeline Research, Planning, TDD, Review, and Commit, with tasks delegated to specialized agents by phase.
Two manually operated doors The plan must be approved before writing code, and the commit must be confirmed before it is uploaded to the repository.
Integrated Safety Review You must enable the security checker whenever the diff involves authentication, user input, databases, or cryptography.
Grouped conventional commits Generate `feat:`, `fix:`, and `refactor:` commits—one per logical block—which must be confirmed before they are applied.

Frequently asked questions

It invokes a planning agent (which generates the task_list), a TDD agent (red-green-refactor cycle), a code review agent, and, when necessary, a security review agent.
Claude won't write any implementation code until you confirm the plan. This is Checkpoint 1: you can request changes before the pipeline moves forward.
This is mandatory whenever the diff triggers security triggers: authentication, user inputs, databases, or cryptography. CRITICAL or HIGH findings must be resolved before committing.
Yes. The skill does not require external MCPs; it operates using the native capabilities of Claude Code and Cowork.
Development Pipeline Orchestrator — TDD-Driven Lifecycle with Claude AI

¿Prefieres escuchar el contenido? Genera la narración de audio con un clic.