implement-expert

Automating software issue implementation involves a 5-phase workflow: audit, plan, implement, verify, and document/close. This manages the full issue lifecycle from backlog to closure, enforcing coding standards via conventional commits and updating project management tools.

Managing code implementation dependencies is achieved through architect gating within the planning phase. This ensures structural integrity before coding begins, handling dependencies and verifying architectural choices.

Yes, you can enforce conventional commits and testing during the development workflow. The verification phase mandates test execution, while the implementation phase enforces coding standards through conventional commit messages.

Yes, issue tracking integration updates project management tools automatically upon completion. It manages the issue lifecycle by syncing status updates and closing issues, while providing detailed implementation notes.

Writing tests and implementation notes for a new feature request is part of the verify and document phases. The workflow executes coding, runs tests for verification, and generates detailed implementation notes upon issue closure.

You should not use an automated agile development workflow for coding tasks that require informal, ad-hoc changes outside a structured issue lifecycle. The strict 5-phase process enforces planning, testing, and documentation, which may be excessive for quick fixes.