teamlead

What problem does it solve? Coordinating multi-role development work on a billing project is error-prone: tasks touch money-related logic, span backend and frontend, and require review and testing discipline. This Skill acts as a teamlead orchestrator that decomposes full-cycle tasks and routes them to the right role skills without writing code itself. ## Core Features & Use Cases - Role-based routing: A routing table maps task signals (pricing, Prisma, UI components, docs, tests, diffs) to the correct delegate skill: /backend, /frontend, /techwriter, /testing, /reviewer. - Billing-specific guardrails: Enforces backend-first sequencing for fullstack work, mandatory review for money-related changes, a 2-round reviewer iteration limit, and escalation to the Architect for ambiguous or business-rule changes. - Pipeline governance: Inherits a core pipeline (stages 0-11) with defined stop points for plan approval, automatic feature-branch commits, and Architect approval for merges to master. - Use Case: You receive a task to add a new usage-based pricing tier. Invoke this Skill to have it decomposed, implemented by backend then frontend, validated by testing, reviewed, and reported end to end. ## Quick Start Invoke the teamlead skill with a task description or a path to a todo file such as docs/todo/NNN-slug.md to have it decomposed and routed through the project roles.