run-implementation-plan

Automating implementation plan execution requires orchestrating batch scheduling, parallel task coordination, and review cycles. This Skill reads a structured plan, finds the next incomplete batch, executes tasks, runs verification, commits changes, and creates pull requests autonomously.

Batch orchestration structures implementation plans into sequential or parallel execution groups. You need it when coordinating long-running software delivery plans that require scheduling independent tasks, managing track ordering, handling task conflicts, and automating branch and PR creation.

Yes, parallel task coordination launches independent implementation agents together while respecting track ordering and task conflicts. It parses plan dependencies, tracks task status, and schedules concurrent execution only for non-conflicting tasks within the same batch.

Verification and code review loops run tests, formatting, linting, and build checks before committing. The workflow reviews changes, fixes issues, executes quality gates, and handles conflicts before automated branch management and pull request creation.

Yes, the implementation plan orchestrator operates without external dependencies. It requires only a structured implementation plan as input and handles plan parsing, task status tracking, conflict handling, quality gate execution, and automated branch and PR management internally.

Autonomous batch execution limitations include reliance on structured plan parsing accuracy and dependency on track ordering rules for conflict handling. Complex task conflicts may require manual intervention if quality gate execution fails or if review cycles cannot automatically fix issues.