develop-feature

Full-cycle feature development workflow automation orchestrates the entire process from ticket ingestion to pull request creation, managing requirements discovery, architectural planning, TDD implementation, QA validation, and automated code reviews to ensure production-ready output.

Enforcing Test-Driven Development (TDD) requires mandatory test writing before code implementation. This approach integrates comprehensive QA validation and architectural review to ensure robust testing and adherence to best practices throughout the feature development cycle.

Yes, this feature development workflow integrates automated code and plan reviews with a rails-architect agent. It ensures adherence to best practices, single-responsibility PRs, and robust testing before completing the pull request creation process.

To ensure single-responsibility pull requests during feature development, the workflow orchestrates requirements discovery and architectural planning, then validates the implementation through comprehensive QA and automated architect-level code reviews before PR creation.

Yes, you can use this TDD workflow for tickets like implementing user profile editing. It breaks down the ticket requirements, mandates writing tests before code, ensures thorough QA validation, and gets it reviewed by an architect before creating a PR.

You should not use an automated end-to-end feature development workflow if your task bypasses standard ticket ingestion, requires skipping TDD or QA validation, or does not need architectural planning and single-responsibility pull request constraints.