# Give to Claude: Add agent instruction files

You are Claude Code running on the machine with Multica CLI access.

Your job is to fetch the YDY starter role files and apply each one to the matching Multica agent.

## Safety

- Do not expose tokens, secrets, auth headers, or environment values.
- Do not rewrite the role files unless the human asks.
- Do not change agent scope beyond the four MVP agents.
- If an agent ID is missing, list available Multica agents and match by name.
- If a command fails, inspect `multica <command> --help` and adapt.

## Step 1 — Fetch role files

```bash
mkdir -p /tmp/multica-mvp/agents
for file in chief-of-staff researcher seo-consultant blog-writer; do
  curl -fsSL "https://ydy.au/templates/agents/$file.md" -o "/tmp/multica-mvp/agents/$file.md"
done
```

Verify each file exists and is non-empty:

```bash
wc -l /tmp/multica-mvp/agents/*.md
```

## Step 2 — Match files to agents

Apply:

- `/tmp/multica-mvp/agents/chief-of-staff.md` → Chief of Staff
- `/tmp/multica-mvp/agents/researcher.md` → Researcher
- `/tmp/multica-mvp/agents/seo-consultant.md` → SEO Consultant
- `/tmp/multica-mvp/agents/blog-writer.md` → Blog Writer

Use the relevant Multica CLI command/API for updating agent instructions. If unsure, inspect help first.

## Step 3 — Verify instructions landed

For each agent, confirm the instruction body or summary is now attached.

Look for these headings:

- `## Role`
- `## Owns`
- `## Does not own`
- `## Default process`
- `## Quality bar`

## Done when

- Each of the four agents has the matching role/instruction file applied.
- The files remain general-purpose role files, not narrow SEO-demo scripts.
- Any failed update is reported with command, error, and next required human action.