coder

Automate code generation for autopilot workflows by delegating implementation to a dedicated coder subagent. It generates concrete implementations, updates modules, and returns the paths of changed files to ensure consistency across your task-by-task development plan.

Header-driven governance is a validation mechanism applied during module refactoring. It ensures that updated code maintains required module headers and verifies API signatures after edits, keeping automated code modifications structurally consistent and compliant.

Yes, you can use automated code generation to write scaffolding and concrete implementations for standalone tasks. It quickly delivers runnable code and specifies changed file paths without requiring a full autopilot workflow integration.

Yes, automated refactoring verifies API signatures after editing code. This validation step is built into the code modification process to ensure that changes across multiple modules do not break existing interface definitions.

The best way to track changed files during task-by-task development is to specify and return their paths after code generation. The coder subagent handles this automatically, ensuring you know exactly which modules were created or modified.

Avoid using an autopilot coder for module updates when your project lacks clear implementation plans or requires manual validation outside of header-driven governance and API signature checks, as it is designed for task-by-task development with specific structural requirements.