feature-implement

To wire feature logic into a runtime, plan which files to modify, attach imports, add docstrings, connect business logic, and verify ruff checks plus end-to-end tests pass for runtime integration.

The best way to implement business logic post-scaffold is coordinating a four-step process: plan file modifications, wire code to the runtime, verify integration with lint and tests, and update the task state.

Integrating new modules with lint and test guards prevents regressions by gating the wiring process with ruff checks and end-to-end verification, ensuring new code maintains design alignment and runtime stability.

Yes, you need type hints and docstrings when wiring feature logic. The implementation process explicitly requires adding docstrings and maintaining type hints to satisfy design alignment and runtime integration checks.

Yes, you can use ruff checks to verify runtime integration. Running ruff checks is a core safeguard during feature implementation to ensure wired business logic meets lint standards before end-to-end verification.

If feature implementation fails end-to-end integration checks, review planned files and consumers, verify imports and type hints, rerun ruff checks, and ensure wired business logic aligns with the original design before updating task state.