implement-change

You can automate code changes and pull request finalization by dispatching sequential subagents that execute tasks one at a time. This prevents parallel conflicts and automatically runs validation checks before finalizing the pull request.

Yes, subagent orchestration dispatches implement-and-validate subagents one at a time for each task in a provided list. This sequential execution ensures each step builds on the previous one without parallel conflicts.

Automated pull request finalization handles CI failure remediation by integrating agent-validator checks and automatically addressing failures for merged pull requests. This ensures validation passes before finalizing the PR.

Yes, this workflow requires predefined implementation task lists, design documentation, and an existing codebase. These inputs provide the necessary context for subagent-based task dispatch and successful feature delivery.

The best way to coordinate implementation tasks and validation checks end-to-end is using sequential task orchestration with integrated validation. It dispatches subagents individually, runs agent-validator checks, and finalizes pull requests automatically.

Yes, automated change implementation works with OpenSpec change archiving by optionally archiving changes if applicable during the workflow. This occurs alongside validation checks and pull request finalization.