workflow-guide_skill

Overview

This skill guides coordination of PM, Frontend, Backend, Mobile, and QA agents for complex projects via a CLI-driven multi-agent workflow. It provides a repeatable sequence for planning, spawning parallel agent tasks, monitoring progress, and final QA review to deliver cross-domain features reliably. The emphasis is on clear API contracts, separated workspaces, and stepwise verification to avoid conflicts.

How this skill works

Start with a PM agent to decompose the request into prioritized tasks and assign workspaces. Spawn domain agents (frontend, backend, mobile, etc.) via the CLI in parallel for same-priority tasks, using background processes and the configured agent mappings. Monitor each agent through progress files and memory tools, confirm API contracts and shared models, then run the QA agent last to validate deliverables and trigger fixes if needed.

When to use it

• Building a feature that touches frontend, backend, and mobile codebases simultaneously
• Coordinating multiple specialist agents across a monorepo or polyrepo setup
• Needing step-by-step guidance for human-in-the-loop multi-agent collaboration
• Projects where clear API contracts and consistent data models are critical
• When separate workspaces are required to prevent file conflicts during parallel work

Best practices

• Always run the PM agent first to produce a prioritized task breakdown
• Spawn same-priority tasks in parallel but use dedicated workspaces per agent
• Define and confirm API contracts before frontend or mobile implementation begins
• Continuously poll progress artifacts (e.g., progress-{agent}.md) to detect drift
• Keep QA as the final step and re-spawn agents to address critical findings
• Prefer the established code exploration/modification tools recommended by your team for consistency

Example use cases

• Implementing a new user onboarding flow that requires backend endpoints, web UI, and mobile screens
• Coordinating a schema change that affects API, frontend forms, and mobile validation logic
• Delivering a payment integration where backend, web checkout, mobile flow, and QA testing must align
• Refactoring shared data models across Next.js and Flutter clients while keeping FastAPI backward compatible
• Rolling out infrastructure changes with Terraform that require backend and mobile adjustments