Example teams

We run Lucitra on our own work with the teams below. Each is a package in the format described in Writing a team package, and each shows a different use of it: a delivery team with defaults only, and operator teams whose actions wait for a person. They are not published, so read them as worked examples to copy from, not as teams to install.

Software

Builds, ships and maintains software.

ceo                     Chief Executive Officer
└── eng-lead            Engineering Lead
    ├── devops          DevOps Engineer
    ├── qa-engineer     QA Engineer
    └── release-manager Release Manager


Schedules	A weekly retro on Mondays (`ceo`), dependency triage on Wednesdays and a monthly security scan (`devops`)
Policies	None. The defaults apply: a finished task pushes its branch and opens a pull request, and a person merges
Integrations	None declared

The simplest shape: a chart, instructions per agent, and schedules. Start here.

Real estate

An operator team: a lead that takes requests, an investment analyst, an opportunity scout and a transaction coordinator.


Schedules	A morning brief and a midday check, and a deadline sweep each weekday. All three are `draft: true`
Gated	Sending messages, submitting an offer, filing a document, writing to the CRM, sharing client data, making a financial commitment, changing policy

Its tools come from a realestate integration Lucitra does not ship, so today the team works from what you give it and reports back. Shows named actions gated before the tools exist.

Health

A clinical documentation team: a lead, chart preparation, a scribe and a coder.


Schedules	Morning chart preparation and an end-of-day queue. Both are `draft: true`
Gated	Writing a note, submitting an order, submitting a claim, changing policy
Autonomous	Reading the chart, notes and transcripts

Its tools come from an ehr integration Lucitra does not ship. Shows a policy where every write waits for a person and every read runs on its own.