implement-feature

Automating feature implementation requires orchestrating a multi-phase pipeline that writes tests, implements code, reviews, and documents. This process uses isolated git worktrees per feature and enforces dependency-based task execution to maintain repeatable delivery.

Managing parallel tasks during feature implementation is best handled by executing dependency-based task waves. This approach processes independent tasks concurrently, logs decisions, and uses isolated worktrees to prevent branch conflicts.

Ensuring architecture alignment during feature implementation involves running a structured pipeline after architectural planning. It enforces iterative review cycles and logs decisions to keep the new code consistent with the project's structural design.

Yes, isolated git worktrees can be used per feature to automate the delivery pipeline. This creates separate working directories for each feature, preventing branch interference while the pipeline handles testing, coding, and documentation.

Running an implementation pipeline after architecture planning ensures the end-to-end delivery follows the established design. It bridges the gap between architectural intent and actual code by enforcing dependency order, testing, and review cycles.

Automated feature delivery with dependency-based task waves is needed when implementing complex features requiring parallel execution and strict architectural alignment. It manages isolated worktrees and iterative reviews to enforce a repeatable process.