recipe-front-build

Autonomous frontend task orchestration coordinates a task-executor, escalation checks, and a quality-fixer to produce committed changes. It manages complex frontend migrations by enforcing a mandatory four-step execution cycle for reliable, traceable results.

The mandatory execution cycle for autonomous frontend workflows consists of four steps: task-executor-frontend, escalation check, quality-fixer-frontend, and commit. This sequence ensures post-implementation verification and consistency with the work plan.

You coordinate subagents for parallel frontend task processing by using an orchestration skill that spawns and manages dedicated execution and quality assurance agents. This enforces sub-agent prompt constraints while consuming work plans.

Yes, you need a work plan before starting autonomous frontend task execution. The workflow enforces mandatory pre-execution prerequisites and consumes a task-set to ensure readiness and maintain an auditable workflow across plans and design docs.

Yes, you can use autonomous orchestration for UI changes requiring design doc traceability. It applies post-implementation verification to ensure consistency with the Design Doc and Work Plan, covering feature work and complex migrations.

A key limitation of subagent orchestration for frontend feature work is its strict dependency on pre-execution prerequisites and consumed task-set management. Without a structured work plan, the enforced four-step execution cycle cannot operate properly.