Run a hackathon on
your own codebase.
The 22 challenges in this repository are worked examples that demonstrate outcome-driven patterns. Use the BYOC authoring kit to design and run a hackathon around your team's actual app, repo, or business outcome.
The BYOC authoring kit.
A structured approach to designing outcome-driven hackathons on real codebases. Define the outcome, map the work, design the stages, and run a facilitated event.
A structured worksheet to define the target outcome, current pain, definition of done, constraints, and demo plan before you build the challenge.
Step-by-step guide for running a BYOC hackathon -- prep, environment setup, timeboxes, demo review, and outcome scorecard assessment.
A reusable definition-of-done and business-impact template. Replace usage metrics as the success measure with actual deliverable assessment.
A worked example showing how to adapt an existing challenge end-to-end through the BYOC kit -- from outcome canvas to scorecard review.
Challenge authoring templates.
Skeleton files matching the canonical track structure. Use these to author your own outcome-driven challenge around your app or repo.
Main track file skeleton with placeholders for outcome, overview, stages, and success criteria.
Stage skeleton with Tasks, Verification, Copilot vs Judgment sections, and navigation placeholders.
Annotated metadata file with inline comments explaining valid values for outcomes, category, difficulty, and prerequisites.
Getting started with BYOC.
Follow these steps to design and run your own outcome-driven hackathon.
- Define your outcome using the Outcome Canvas. What work result do you want teams to produce?
- Map the work into 3-5 stages or phases that progress toward the deliverable. Each stage should be completable in 45-90 minutes.
- Author your challenge using the templates. Fill in the track file, stage files, and meta.yml with your outcome framing.
- Prepare the environment. Set up a Codespace, container, or local dev environment with your app's repo, dependencies, and any required credentials.
- Run the hackathon using the Facilitator Runbook. Timebox each stage, facilitate blockers, and run a demo-driven retrospective.
- Assess the outcome with the Outcome Scorecard. Did teams ship a demonstrable deliverable? Can they articulate the business impact?
Related resources.
The full BYOC README with motivation, use cases, and links to all kit components.
The canonical conventions for track file structure, sections, and metadata. All BYOC challenges must follow this.
Explore the 22 worked-example challenges to see the outcome-driven pattern in action across different categories.