recipe-front-adjust

Orchestrate UI adjustments by coordinating a parent session with bounded subagents for fact gathering, planning, and quality checks. This workflow manages write-sets and enforces strict stop-points to ensure user review before applying frontend edits.

Agent orchestration for frontend verification is a process where a parent session delegates fact gathering and quality checks to bounded subagents. It isolates changes, confirms write-sets, and applies staged verification to ensure UI edits are traceable and validated.

Plan minimal commits for frontend components by using bounded subagents to analyze external resources and gather facts. The parent session then reviews the proposed write-set at defined stop-points before proceeding with targeted UI adjustments.

You need staged verification for UI changes when implementing complex frontend edits that require traceability and risk containment. It enforces written confirmation workflows and stop-points so you can review subagent plans and quality checks before finalizing updates.

Yes, you can use bounded subagents to isolate frontend planning and quality checks from the main session. Subagents handle fact gathering and verification, returning results to the parent session which manages the actual write-set and edits.

UI adjustment workflows require write-set confirmation to ensure changes remain traceable and isolated. By validating the exact modifications before execution, the parent session maintains controlled orchestration and prevents unchecked edits to frontend components.