implement

Automate feature implementation by using a phase-driven workflow that injects CLAUDE.md rules, runs pre-implementation setup, and executes validators across phases 0 to 4. This enforces compliance and fixes violations before outputting a structured completion report.

The best way to enforce project-specific rules is through a pre-implementation setup phase that reads CLAUDE.md configurations, collects local supplements, and prepares the environment. This ensures all subsequent code changes comply with deterministic linting standards.

Automatic validation works by applying linters and semantic validators across structured implementation phases. It detects violations, attempts automatic fixes where possible, and generates a completion report to verify code compliance before finalizing the feature.

Yes, a CLAUDE.md file is required for automated feature implementation. The workflow specifically relies on Phase 0 rule injection to read project-specific CLAUDE rules and local supplements to establish the validation baseline for code changes.

Yes, you can fix linting and semantic violations automatically. The integrated validation loop runs deterministic linters and semantic validators during the implementation phases and fixes violations where possible before generating a structured report.

A limitation of phase-driven implementation is its strict dependency on CLAUDE.md rule injection and local supplements. Projects lacking these configuration files or requiring phases outside the 0 to 4 workflow structure may not integrate properly with the automated validation loop.