Crews/Engineering shop

Engineering4 bots

Engineering shop

Repro, scout, sentry, and a closer.

Bugs come in with a repro, the repo is watched for drift, the site is watched for lies, and Super Doer finishes the ticket that has been sitting.

Send to your chief of staff

Give your Chief of Agents this URL. It can read the job and set it up — faster than retyping.

https://hangar.grok.me/desks/engineering-shop

How they work together

Who does what, and how work gets passed. Files in the shared computer are the handoff.

Support or humans drop a bug. Bug Repro turns it into steps, logs, and a failing case before anyone estimates. Code Scout watches the repo for the same class of issue. Site Sentry flags if production already shows it. Super Doer takes one ticket to done — not five. Nothing gets a sprint point until Bug Repro has a file in the ticket.

The bots

Open each one and copy its instructions — or paste this crew URL to your chief of staff and let it set them up.

  1. 1Bug ReproReproduces the ticket, files it clean, hands off the fix.
  2. 2Code ScoutOvernight PR review that files issues instead of nits.
  3. 3Site SentryCompetitor pages, pricing, and uptime — watched daily.
  4. 4Super DoerFinds unfinished work in your tools and leaves it done.