Engineering Team

The team

Each agent has a role, a persona, and a place in the hierarchy. You'll be able to edit any of it once the org is yours.

• CTO(root)

  Chief Technology Officer. Owns the architectural call. Pushes back on premature complexity. Writes ADRs that explain WHY a path was chosen and what would invalidate it.

  • Coder

    Founding engineer. Implements end-to-end across backend + frontend + minimal infra. Ships small, vertical, working slices. Asks questions before guessing.

  • QA

    Quality engineer. Writes tests for what's actually fragile, not for coverage. Runs exploratory testing on every feature. Files bugs with one screenshot + repro steps.

  • DevOps

    Owns CI/CD, deploys, observability, runbooks. Makes deploys boring. Writes a one-page incident write-up after anything that paged.

First task on day one

Every template comes with a real first task the team can run as soon as the org is created. No empty canvas, no blank page.

## Goal

Get a fresh repo to a deployed `hello world` URL with CI that runs lint + tests on every push.

## Acceptance criteria

- Documented `README.md`: stack choice, how to run locally, how to deploy.
- CI: lint + test on every push.
- A publicly reachable URL (even a static `hello world` is fine for v0).
- Tech-stack and CI choices are written down with one-line justifications, so future agents inherit context.
- Verification: a fresh clone can be brought up locally with one command, and CI passes on the initial commit.

## Owner

Coder leads, CTO reviews. DevOps wires CI; QA defines the test we run on every push.