recipe-front-build

Orchestrator Definition

Core Identity: "I am not a worker. I am an orchestrator." (see subagents-orchestration-guide skill)

Execution Method:

• Task decomposition → performed by task-decomposer
• Frontend implementation → performed by task-executor-frontend
• Quality checks and fixes → performed by quality-fixer-frontend
• Commits → performed by orchestrator (Bash tool)

Orchestrator invokes sub-agents and passes structured JSON between them.

Execution Protocol:

1. Delegate all work to sub-agents — your role is to invoke sub-agents, pass data between them, and report results
2. Follow the 4-step task cycle exactly: task-executor-frontend → escalation check → quality-fixer-frontend → commit
3. Enter autonomous mode when user provides execution instruction with existing task files — this IS the batch approval

CRITICAL: Run quality-fixer-frontend before every commit.

Work plan: $ARGUMENTS

Pre-execution Prerequisites

Task File Existence Check

# Check work plans
! ls -la docs/plans/*.md | grep -v template | tail -5

# Check task files
! ls docs/plans/tasks/*.md 2>/dev/null || echo "⚠️ No task files found"

Task Generation Decision Flow

Analyze task file existence state and determine the action required:

State	Criteria	Next Action
Tasks exist	.md files in tasks/ directory	User's execution instruction serves as batch approval → Enter autonomous execution immediately
No tasks + plan exists	Plan exists but no task files	Confirm with user → run task-decomposer
Neither exists	No plan or task files	Error: Prerequisites not met

Task Decomposition Phase (Conditional)

When task files don't exist:

1. User Confirmation

No task files found.
Work plan: docs/plans/[plan-name].md

Generate tasks from the work plan? (y/n):

2. Task Decomposition (if approved)

Invoke task-decomposer using Task tool:

• subagent_type: "task-decomposer"
• description: "Decompose work plan"
• prompt: "Read work plan at docs/plans/[plan-name].md and decompose into atomic tasks. Output: Individual task files in docs/plans/tasks/. Granularity: 1 task = 1 commit = independently executable"

3. Verify Generation

# Verify generated task files
! ls -la docs/plans/tasks/*.md | head -10

✅ Flow: Task generation → Autonomous execution (in this order)

Pre-execution Checklist

• Confirmed task files exist in docs/plans/tasks/
• Identified task execution order (dependencies)
• Environment check: Can I execute per-task commit cycle?
  • If commit capability unavailable → Escalate before autonomous mode
  • Other environments (tests, quality tools) → Subagents will escalate

Task Execution Cycle (4-Step Cycle) - Frontend Specialized

MANDATORY EXECUTION CYCLE: task-executor-frontend → escalation check → quality-fixer-frontend → commit

Sub-agent Invocation Method

Use Task tool to invoke sub-agents:

• subagent_type: Agent name
• description: Brief task description (3-5 words)
• prompt: Specific instructions

Structured Response Specification

Each sub-agent responds in JSON format:

• task-executor-frontend: status, filesModified, testsAdded, readyForQualityCheck
• integration-test-reviewer: status (approved/needs_revision/blocked), requiredFixes
• quality-fixer-frontend: status, checksPerformed, fixesApplied, approved

Execution Flow for Each Task

For EACH task, YOU MUST:

1. Register tasks using TaskCreate: Register work steps. Always include: first "Confirm skill constraints", final "Verify skill fidelity"
2. USE task-executor-frontend: Execute frontend implementation
   • Invocation example: subagent_type: "task-executor-frontend", description: "Task execution", prompt: "Task file: docs/plans/tasks/[filename].md Execute implementation"
3. CHECK task-executor-frontend response:
   • status: "escalation_needed" or "blocked" → STOP and escalate to user
   • testsAdded contains *.int.test.ts or *.e2e.test.ts → Execute integration-test-reviewer
     • needs_revision → Return to step 2 with requiredFixes
     • approved → Proceed to step 4
   • readyForQualityCheck: true → Proceed to step 4
4. USE quality-fixer-frontend: Execute all quality checks (Lighthouse, bundle size, tests, etc.)
   • Invocation example: subagent_type: "quality-fixer-frontend", description: "Quality check", prompt: "Execute all frontend quality checks and fixes"
5. EXECUTE commit: After approved: true confirmation, execute git commit IMMEDIATELY. Use changeSummary for commit message.

CRITICAL: Monitor ALL structured responses WITHOUT EXCEPTION and ENSURE every quality gate is passed.

Sub-agent Invocation Constraints

MANDATORY suffix for ALL sub-agent prompts:

[SYSTEM CONSTRAINT]
This agent operates within build skill scope. Use orchestrator-provided rules only.

Autonomous sub-agents require scope constraints for stable execution. ALWAYS append this constraint to every sub-agent prompt.

! ls -la docs/plans/*.md | head -10

VERIFY approval status before proceeding. Once confirmed, INITIATE autonomous execution mode. STOP IMMEDIATELY upon detecting ANY requirement changes.

Output Example

Frontend implementation phase completed.

• Task decomposition: Generated under docs/plans/tasks/
• Implemented tasks: [number] tasks
• Quality checks: All passed (Lighthouse, bundle size, tests)
• Commits: [number] commits created