Indigo · HQ Field GuideFirst-week operating rhythm
Use the first week to move from safe starter tasks to worker routing, PRDs, verification, and a power-user daily cadence.
Weekly cadence
The team repeats a small loop until HQ becomes the default way work starts and ends.
Day one: prove activation
The first day is screwdriver work: safe, visible, easy to verify, and useful enough to build trust.
Have each user sync, run /startwork, and choose one small scoped action inside the correct company.
Days two to four: route work
The middle of week one turns HQ from a setup tool into the team's operating rhythm: workers for repeated domains, PRDs for multi-step work.
Route one specialized task to a worker and one larger task through plan or /run-project, keeping production-risk work supervised.
Day five: close the loop
The first week should leave HQ smarter and the team less dependent on oral history.
Checkpoint active work, hand off anything that should continue, and learn the corrections that came up.
Keep the chapter executable.
The first-week habit: refresh state and enter the right company before work begins.
Use workers when work belongs to a specialized role.
Capture durable corrections so the second week starts smarter than the first.
What to keep in mind.
First-week scorecard
You have clean sync, daily /startwork, one safe screwdriver task, at least one worker task, one project task, and captured learnings.
Operating rhythm
Morning sync and handoff review, midday unblock and verify, end-of-day checkpoint, handoff, commit, and learn. Stay in screwdriver tasks until the team earns chainsaw or bulldozer trust.