implement

To turn an approved spec into Rails code, use a phase-based implementation workflow that creates a todo list, opens a feature branch, and builds features with small, focused commits. It enforces tests, linting, and security scans throughout.

Automating RuboCop and Brakeman scans during Rails feature development is handled by running targeted and full test suites, linting, and security checks after each change. This structured workflow enforces verification before finalizing commits.

DHH-style code review for a Rails codebase works by invoking a review agent that provides iterative feedback. It applies suggestions across multiple iterations, reverting or pausing work on persistent failures while documenting issues.

Yes, passing tests and a clean Git working tree are explicit prerequisites before implementing a new feature. The workflow enforces these rules to prevent broken builds and ensure a verified Rails codebase.

When Brakeman or tests fail during Rails implementation, the workflow applies failure-handling rules that revert or pause work. It documents the persistent issues encountered during the iterative DHH review process.

This implementation workflow applies to Rails projects following AFAL conventions. It translates an approved architecture specification into focused commits, tests, linting, security scans, and a DHH-style code review.