Turn your own codebase into
a Copilot challenge.
The catalog gives you 30 examples. The BYOC kit helps you take the same format and apply it to work your team already cares about.
Everything you need to build the session.
Start with the result your team needs. Then split the work into stages, prepare the environment, and decide how you will judge the final demo.
Use this worksheet to pin down the problem, the expected result, the constraints, and what the team will show in the final demo.
A practical runbook for preparation, environment setup, timing, the demo, and the final scorecard review.
A definition-of-done template that judges the work produced, instead of counting prompts or measuring tool usage.
See how one challenge moves from the first outcome canvas to the final scorecard review.
Start from a template.
These files match the track structure used across the catalog. Replace the placeholders with your own work and context.
The main track file, with space for the goal, overview, stages, and success criteria.
A stage file with sections for tasks, checks, human judgment, and navigation.
An annotated metadata file covering the goal, category, difficulty, and prerequisites.
Build your first session.
Work through these steps in order. You can come back and adjust them as the challenge takes shape.
- Define the result with the Outcome Canvas. Be specific about what the team should produce.
- Split the work into 3-5 stages. Give each stage one useful result that a team can finish in 45-90 minutes.
- Write the challenge with the templates. Fill in the track, stage, and metadata files.
- Prepare the environment. Set up a Codespace, container, or local development environment with the repository, dependencies, and required credentials.
- Run the session with the Facilitator Runbook. Keep the stages on time, help with blockers, and review the final demos.
- Review the result with the Outcome Scorecard. Check whether the work runs, solves the stated problem, and can be explained clearly.
Related resources.
The full BYOC guide, with background, common uses, and links to every part of the kit.
The required structure for track files, sections, and metadata.
Browse 30 examples across product delivery, modernization, automation, and Azure platform work.