chordlens-orchestrator

Phased development orchestration coordinates sequential stages from planning to GitHub integration, unifying frontend and backend work. It applies structured phases for task classification, implementation, QA, and cleanup to ensure reproducible delivery.

You can automate code review loops by applying prompt-based evaluation between planning, implementing, and QA phases. This orchestrator routes tasks and triggers automated critiques to enforce quality gatekeeping before shipping code.

The best way to manage development workspaces is using a dedicated directory to store tasks, plans, critiques, and reports. This workspace-driven approach maintains context across planning, implementation, and QA phases for full reproducibility.

To coordinate end-to-end workflows, run structured phases sequentially: context check, task classification, planning with critique, implementation, QA, and finally GitHub integration for pull request creation, followed by workspace cleanup.

Yes, phased orchestration aligns stakeholder communication by routing tasks through structured QA feedback loops. It integrates automated prompts between implementers and QA to ensure quality gatekeeping before communicating delivery status.

Task orchestration requires a workspace directory to store plans and reports but does not specify a rigid project structure. It uses prompt-based evaluation and task routing to manage phase transitions cleanly within your existing codebase.