executing

Automating task execution pipelines involves orchestrating a three-stage subagent pipeline for implementation, spec review, and quality review. This Skill manages task dependencies and executes tasks in batches with user-driven checkpoints for completion control.

A multi-stage subagent pipeline coordinates native Task agents through implementation, spec review, and quality review stages. Each task passes through structured execution phases, ensuring code meets specifications and quality standards before batch progression.

Resuming batch task processing requires progress persistence via a `progress.md` file. The pipeline saves execution state and task dependencies, allowing you to resume session work and continue batch completion from user-driven checkpoints.

Yes, this task execution pipeline requires native Task coordination and strict adherence to conventional commit standards. Subagents must follow these standards during the implementation and quality review stages to ensure batch processing integrity.

Executing a development plan requires loading a task plan located at a specified markdown path. The pipeline then automates feature development by having subagents implement tasks, review code against specifications, and perform quality checks with automated progress tracking.

Subagent pipelines rely on native Task coordination and require user intervention at batch completion checkpoints. Progress persistence depends entirely on the `progress.md` file, meaning execution cannot proceed autonomously without user-driven validation between batches.