code-implementer

Plan-driven development enforces coding standards by applying linting and type checks after each implementation step, ensuring traceability and preventing progression to validation until the current step meets project conventions.

Yes, you can use this with standard project context files like CLAUDE.md or project-context.md. You load these files alongside the validated plan to apply project conventions and coding standards during implementation.

This approach differs from ad-hoc coding by enforcing strict task tracking and traceability. It requires a validated plan upfront and halts progression to validation until lint, typecheck, and convention checks pass for each step.

Run lint and typecheck after completing each individual step of the implementation plan. You must resolve any convention violations and show the resulting diff for review before progressing to the validation phase.