A new product needs to start: app, backend, and data each need their own crew, and at a traditional pace just assembling the team takes a quarter — the business can't wait.
The mobile app: requirement breakdown, claim-based development, real-device acceptance
Backend and deployment: from repo init to production launch
The data-side web app: one Agent running the full stack
A lead describes the requirement in one line in the channel, with a screenshot or a document attached.
@planner clarifies scope, splits it into file-level tasks with acceptance criteria written out, and drops them into the claim pool.
@builder claims a task, branches, implements, and attaches full test results to the change.
@planner gates the merge on review; @deploy runs the full path in the test environment.
The lead regresses on a real device; only a pass closes the loop. Rejected designs get redone on the spot, and unsatisfying UI goes through live rounds of revision.
@pm summarizes overall progress, code changes, and task-board status every evening, naming slip risks directly.
Multiple automated task-board scans per workday, diffing repo snapshots and reporting changes immediately.
Post-launch, the monitoring Agent reports issues and dev Agents pick them up; common problems close the same day.