engineering-team

EngineeringTeam

Give your AI coding agent an expert software engineering team.

EngineeringTeam is a repo-first workflow layer that makes one coding agent operate like a coordinated panel of software engineering experts. For each task, a lead engineer frames the problem, selects the smallest useful set of specialists, gets them oriented on the repo and affected contracts, gates the decision with evidence, and only then makes the targeted implementation or hands back a diagnosis.

Stop asking one agent to guess. Give it the right expert panel, shared repo understanding, and an evidence gate before it edits.

⚡ In thirty seconds

Most coding agents are fast, but speed is not judgment. Real engineering work needs the right mix of skills: someone to map ownership, someone to test the contract, someone to challenge weak evidence, and domain specialists for security, performance, migration, architecture, or release risk when those risks are real.

EngineeringTeam turns that team habit into a reusable skill that works across the agent you already use. It does not add a runtime service, network calls, or session-start magic. You invoke engineering-team when a task deserves expert coordination: it chooses the right panel, makes the panel understand the problem from source evidence, and produces compact, human-reviewable artifacts as it goes.

That panel can deliver a PR-ready implementation, a read-only diagnosis, a repo map, a hypothesis matrix, a log report, a performance probe plan, or a handoff for another session. The point is not “change code” versus “understand code.” The point is: assemble the right experts, establish shared understanding, then make the smallest safe move.

Read-only mode means no edits; it does not mean low rigor. Trivial local explanations can use L0, while broad codebase analysis, root-cause work, performance analysis, protected-boundary review, migration review, release planning, and multi-component PR review still use L2-L5 depth according to complexity and risk.

Use handoff when you want the current task transferred to another agent or a fresh session. It compacts the work into a continuation document with decisions, evidence, open questions, artifact links, suggested skills, and next actions.

Specialist agents are selective, not mandatory. EngineeringTeam does not spawn a fixed committee; it forms the smallest expert panel that covers the task's distinct risks.

🧠 How it works

flowchart LR
    request[User request] --> lead{Lead engineer intake}

    lead --> mode{Outcome needed?}
    mode -->|Fix / feature / refactor| impl[Implementation mode]
    mode -->|Understand / debug / logs / perf| analysis[Read-only analysis mode]
    mode -->|Continue elsewhere| handoff[Handoff mode]

    impl --> panel[Select expert panel]
    analysis --> panel
    panel --> depth[Assign L0-L5 depth]

    depth --> atlas[Repo Atlas]
    atlas --> brief[Component Brief]
    brief --> contracts[Contract Graph]
    contracts --> evidence[Evidence Ledger]
    evidence --> gate{Implementation Gate}
    gate -->|Pass| patch[Small safe patch]
    gate -->|Read-only| report[Diagnosis / report / next probes]
    patch --> verify[Verification Report]
    report --> closeout[Run Ledger / Context GC]
    verify --> closeout

    handoff --> capsule[Continuation document]

🧭 Pick the right workflow