ai-ad-flow-orchestrator

Development flow selection depends on your task type: backend changes use BE_DEV_FLOW, frontend changes use FE_DEV_FLOW, API fixes use API_FIX_FLOW, testing use TEST_HARDEN_FLOW, documentation use DOC_FREEZE_FLOW, refactoring use REFACTOR_FLOW, or full-stack work use FULL_FLOW. The orchestrator auto-detects the appropriate flow and outputs the complete command sequence.

Each flow sequence includes ordered commands to execute, local test commands to verify changes, and a freeze checklist for integration readiness. The orchestrator produces flow_type mapping, explicit command_sequence steps, and SoT alignment requirements to guide execution from task start through deployment readiness.

Yes. The orchestrator supports BE_DEV_FLOW, FE_DEV_FLOW, API_FIX_FLOW, and FULL_FLOW scenarios. Provide your task description and it detects the applicable flow type, then produces the corresponding command sequence, test guidance, and freeze checklist for your specific context.

Provide a task description. The orchestrator analyzes it to determine flow_type, generate ordered command_sequence, define local_test_commands, and produce a freeze checklist. Optional inputs and step-skipping are supported for customized execution plans.

Flow orchestration maps explicit flow_type decisions to SoT alignment requirements, producing ordered command sequences and freeze checklists that verify state consistency. This ensures development steps follow canonical patterns and integration readiness before deployment.

Individual flows (BE_DEV_FLOW, FE_DEV_FLOW, API_FIX_FLOW, etc.) target specific layers or concerns with scoped command sequences. FULL_FLOW orchestrates cross-stack changes, coordinating backend, frontend, and API steps in integrated sequence with unified freeze checklist and test requirements.