dev-team

Dev Team — Dev → QA → Reviewer Loop

This skill drives one unit of work — a spec, ticket, finding, or change request — from its written spec to a committed, reviewed result. It does this by standing up a small agent team and running it through a bounded loop: a Dev implements, a QA verifies ("trust nothing"), a Reviewer does the code review and creates the commit. On any failure the loop sends the Dev the specific feedback, up to a cycle cap, then escalates. Fire it off and it builds the team for you.

It is the reusable core of a rigorous implementation flow. You can fire it off on whatever you're working on right now, and implement-full-spec calls it once per subtask before layering on its own stacking, PR, and review-response machinery.

When to use this skill

Use it when the operator wants a change implemented with rigor — built, independently verified, and code-reviewed before it lands — rather than a quick inline edit. Common phrasings:

• "Implement this spec with a dev → QA → review loop."
• "Fire off the dev team on this task."
• "Use agents to build this and verify it before committing."
• "Drive this change through dev, then QA, then code review."

It is the wrong skill when:

• The change is a one-line tweak you can make and verify directly — the loop's overhead buys nothing.
• The work is a parent ticket with many subtasks that each want their own PR → use implement-full-spec, which calls this loop per subtask.
• The operator wants synchronous pair-programming → just work alongside them.

What this loop needs (the contract)

Before dispatching the first agent, pin these. They are the inputs every role agent inherits — the prompt is the contract, so gather them up front:

Input	What it is
Workspace	The absolute path the agents work in (a worktree or a checkout) and the branch. Agents must stay inside it.
Verbatim spec	The full spec for this unit of work — severity, file paths, description, impact, and every remediation bullet. Never summarize; the prompt is the contract.
IN/OUT-of-scope partition	For every remediation bullet, mark it IN SCOPE or OUT OF SCOPE (with a proposed follow-up name). Bullets needing infrastructure outside the repo are OUT OF SCOPE.
Canonical checks	The exact commands the operator expects to be green: typecheck, lint, the specific test suites, integration tests if any.
Commit terminus	The loop ends at a commit on the branch. Pushing / opening a PR is the caller's job — the loop does not push. (implement-full-spec pushes and opens the PR after the loop returns.)