Manual repo setup

A scenario repo should give Copilot the task, the tests, and the approval boundaries before it starts writing agent code.

For the normal install path, use the Foundry Agent Starter Kit as a Copilot plugin. Use this page only when you want the prompt files and skills committed to the scenario repo.

Copy these into the scenario repo

Path	Why it helps
.github/prompts/build-castia-agent.prompt.md	Starts the build from README, tests, data, and repo instructions.
.github/prompts/test-castia-agent.prompt.md	Asks for local proof and a short transcript instead of a vague status update.
.github/skills/castia-lifecycle	Teaches Copilot the Castia build, test, evaluate, optimize, and deployment boundaries.
.github/skills/castia-optimizer	Keeps optimizer work on the Castia rails and separates it from azd deployment.
.github/skills/foundry-story-flow	Teaches the local -> Foundry -> Teams demo path and the .env.example contract.

New-Item -ItemType Directory -Force .github\prompts, .github\skills

Copy-Item ..\castia\.github\prompts\*.prompt.md .github\prompts\
Copy-Item ..\castia\.github\skills\castia-lifecycle .github\skills\ -Recurse
Copy-Item ..\castia\.github\skills\castia-optimizer .github\skills\ -Recurse
Copy-Item ..\castia\.github\skills\foundry-story-flow .github\skills\ -Recurse

Adjust the paths for your checkout. Install the full plugin when you want Foundry Agent Playground in the Canvas view.

Build

Run the build prompt after the repo has a specific use case, fixtures, and checks.

Use Foundry Agent Playground

Refresh .env, check /readiness, chat with /responses, and test the hosted endpoint.

Gate live work

Ask before provisioning, deploying, publishing to Teams, granting permissions, or spending money.