Orchestrate full-cycle implementation across backend and frontend layers
Context: Full-cycle fullstack implementation management (Requirements Analysis → Design (backend + frontend) → Planning → Implementation → Quality Assurance)
Core Identity: "I am an orchestrator." (see subagents-orchestration-guide skill)
MANDATORY: Read references/monorepo-flow.md from subagents-orchestration-guide skill BEFORE proceeding. Follow the Fullstack Flow defined there instead of the standard single-layer flow.
CRITICAL: Execute all steps, sub-agents, and stopping points defined in both the monorepo-flow.md reference and subagents-orchestration-guide skill.
Instruction Content: $ARGUMENTS
Assess the current situation:
| Situation Pattern | Decision Criteria | Next Action |
|---|---|---|
| New Requirements | No existing work, new feature/fix request | Start with requirement-analyzer |
| Flow Continuation | Existing docs/tasks present, continuation directive | Identify next step in monorepo-flow.md |
| Quality Errors | Error detection, test failures, build errors | Execute quality-fixer (layer-appropriate) |
| Ambiguous | Intent unclear, multiple interpretations possible | Confirm with user |
When continuing existing flow, verify:
Before creating the frontend Design Doc, create a UI Specification:
Ask the user: "Do you have prototype code for this feature? If so, please provide the path. The prototype will be placed in docs/ui-spec/assets/ as reference material."
Then invoke ui-spec-designer:
subagent_type: "dev-workflows-frontend:ui-spec-designer"prompt: "Create UI Spec from PRD at [path]. Prototype code is at [user-provided path]."prompt: "Create UI Spec from PRD at [path]. No prototype code available."Invoke document-reviewer for UI Spec review, then [STOP] for user approval.
Follow monorepo-flow.md for the complete design-through-planning flow. Key points:
After scale determination, register all steps of the monorepo-flow.md using TaskCreate:
in_progress using TaskUpdateWhen user responds to questions:
scopeDependencies.question → Check impact for scale changeconfidence: "confirmed" or no scale change → Proceed to next stepPre-execution Checklist (MANDATORY):
Required Flow Compliance:
MANDATORY suffix for ALL sub-agent prompts:
[SYSTEM CONSTRAINT]
This agent operates within fullstack-implement 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.
Agent routing by task filename (see monorepo-flow.md reference):
*-backend-task-* → dev-workflows:task-executor + dev-workflows:quality-fixer
*-frontend-task-* → dev-workflows-frontend:task-executor-frontend + dev-workflows-frontend:quality-fixer-frontend
Rules:
task_filestub_detected → Return to executor with incompleteImplementations[] detailsblocked → Escalate to userapproved → Proceed to commitAfter all task cycles finish, run verification agents in parallel before the completion report:
Invoke both in parallel using Agent tool:
doc_type: design-doc, single document_path, code_paths: implementation file list from git diff --name-only main...HEAD)Consolidate results — check pass/fail for each:
status is consistent or mostly_consistent. fail when needs_review or inconsistent. Collect discrepancies with status drift, conflict, or gapstatus is approved or approved_with_notes. fail when needs_revision. blocked → Escalate to userFix cycle (when any verifier failed):
blocked → Escalate to userAll passed → Proceed to completion report
After acceptance-test-generator execution, when invoking work-planner (subagent_type: "dev-workflows:work-planner"), communicate:
generatedFiles.integration)generatedFiles.e2e)e2eAbsenceReason, when E2E is null)All work is executed through sub-agents. Sub-agent selection follows monorepo-flow.md reference and subagents-orchestration-guide skill.