feature-loop

Feature delivery orchestration coordinates the entire workflow from intake through implementation, shipping, PR monitoring, and retro follow-up automatically. It routes requests based on clarity and scope, delegates to TDD or tidy-first methods, and tracks outcomes until merge or close is resolved.

Implementation routing delegates behavior changes to TDD and structural changes to tidy-first, ensuring work starts with the right method. This deterministic handoff approach routes tasks based on the nature of the change, applying test-driven development for behaviors and structural cleanup for refactoring.

PR monitoring tracks pull requests until merge or close is resolved without performing merges itself. The pipeline hands off to shipping for quality gates and PR readiness first, then monitors the PR status as a safe delegation step with explicit merge-ready stopping conditions.

Automated retrospective follow-up is included as the final stage of the feature delivery loop. After shipping and PR monitoring resolve to merge or close, the workflow triggers post-merge follow-up actions, completing the end-to-end cycle from initial request intake.

Single-change requests with unclear requirements are handled through intake triage, which evaluates clarity, scope, and design uncertainty. The intake decisioning process determines whether the request is light or heavy, then explicitly routes to the appropriate next step for requirement clarification before implementation begins.

End-to-end feature delivery loops are designed for single-change requests, not multi-change batches or complex cross-system migrations. The workflow requires deterministic handoffs and explicit stopping conditions, meaning it should not be used when you need to perform merges yourself or when changes lack clear acceptance criteria.