Multi-project request examples

Add a documentation source to MSP

Captain says:

Create private repo Leonard-Data/firstmate-docs from the MSP template and register it with MSP.

Firstmate does:

creates the private source repository
seeds the documentation structure
pushes the source content
updates MSP Portal sources.yml
runs source validation and build checks
opens the MSP registration pull request

Why this is multi-project: the source repo owns the docs, while MSP owns the portal registration and generated output.

Split investigation from implementation

Captain says:

Find why the portal search misses new docs pages. If the fix is obvious, tell me what it is before changing code.

Firstmate should assign a scout first because the cause may be source metadata, sync, search indexing, or generated routing. After the report, the captain can approve implementation in the correct repository.

Assign domain work to a second mate

Captain says:

Have the Power Platform second mate update the component standards docs and bring me the PR.

Firstmate should route the task to the second mate whose charter covers Power Platform. The second mate handles its own project copy and returns the outcome through the parent channel.

Parallel independent changes

Captain says:

Update Firstmate setup docs and fix the MSP homepage copy.

Firstmate can split this into two workers when the files and outcomes are independent:

one worker changes the docs source
one worker changes MSP Portal copy

Firstmate still reports the results together when the work reaches review.