Quick link: https://gh.io/msft-hackathon-2026
Welcome! π This repository is the home base for one of the three hackathon challenges. It's where ideas for this challenge get submitted, where the project board lives, and where teams hand in their final projects.
β‘οΈ Submit an idea Β· See the board Β· Browse all ideas
Software teams have spent years building rituals around planning and tracking work β issues, boards, standups, estimates, retros. Then coding agents arrived and started doing some of the work. So: what does good collaboration look like when part of your team isn't human? Build something that answers that, using GitHub's planning and tracking tools (Issues, Projects, milestones, sub-issues, Actions, the GraphQL API) together with AI agents.
That's deliberately broad. A dashboard, a bot, a workflow, a Copilot extension, a genuinely better board layout β all fair game.
These are prompts, not categories. They exist because a blank page is hard, not because your idea has to fit one of them. If yours sits between two of them, or somewhere else entirely, that's a good sign β pick the closest when you submit (or skip it) and describe what you actually mean in the issue.
| Theme | Things it might look like |
|---|---|
| ποΈ Planning & tracking | Issues, Projects, milestones, roadmaps, estimation |
| π€ Agentic workflows | Copilot coding agent, AI-assisted planning, triage, review |
| βοΈ Automation | Actions, webhooks, bots, the GraphQL API |
| π Insights & metrics | Dashboards, reporting, velocity, project analytics |
| π Onboarding & docs | Getting new contributors productive fast |
| βΏ Accessibility & inclusion | Collaboration that works for everyone |
The theme is only used for grouping and browsing the board. Nothing is judged on it, and nobody will tell you your idea is in the wrong one.
Even if you already know what you're building, submit it. Two reasons:
- It gets you hands-on with Issues and Projects, which is half the point of this challenge.
- Every idea goes into a shared pool. Ideas nobody has time to build are up for grabs β and we keep the pool for next year.
Rough ideas are welcome. You'll be asked what problem it solves, roughly which theme it's closest to, and where an agent does real work. "Not sure yet" is a valid answer to that last one β organizers will help shape it.
Your code lives wherever you want β a separate repo is completely fine and usually easier.
You're encouraged to track your team's work here as team task issues so you're actually practising the thing the challenge is about. This is optional, and there's a tradeoff worth understanding: everything in this repo is visible to every other participant. Some teams like that β you can see what others are trying and borrow ideas. Some teams would rather work quietly. Both are fine. If you'd rather keep your day-to-day work private, use your own repo's board and only submit the idea and final submission issues here.
One per team. Submit before the deadline even if you're still polishing β you can edit the issue right up until judging.
Everything lands on the Ideas & Submissions board.
Items move through these statuses:
| Status | Meaning |
|---|---|
| π‘ Idea submitted | Just proposed, waiting on organizer triage |
| β Triaged | Reviewed β open for any team to adopt |
| π Claimed by team | A team has picked it up |
| π§ In progress | Actively being built |
| π¦ Submitted | Handed in for judging |
| π Judged | Judges have reviewed it |
Alongside Status, each item has Submission type, Theme, Team, Effort, and β for finished projects β Code repo and Demo link. Try grouping the board by Theme or Team to see how the same items tell different stories.
Ideas labelled status: looking-for-team
are unclaimed. To take one: comment on the issue saying your team is claiming it, and an organizer will
assign you and flip it to status: claimed. Credit the original author in your submission.
| Label | Meaning |
|---|---|
type: idea |
A submitted challenge idea |
type: project-submission |
A team's final submission |
type: team-task |
Work item a team is tracking |
type: example |
Seeded by organizers as an example β please don't edit these |
theme: * |
Roughly what the item is about β a browsing aid, nothing more |
status: looking-for-team |
Unclaimed β any team may adopt it |
status: claimed |
A team is on it |
needs: triage |
Waiting on organizer review |
Organizers: replace the placeholders below before sharing the repo.
| Milestone | When |
|---|---|
| Idea submissions open | _TBD_ |
| Idea submission deadline | _TBD_ |
| Hackathon starts | _TBD_ |
| Final project submission deadline | _TBD_ |
| Demos & judging | _TBD_ |
| Criterion | What we're looking for |
|---|---|
| Answers the challenge | Does it actually say something about collaboration in the agentic age? |
| Agentic depth | Are agents doing meaningful work, with sensible human checkpoints β or is AI bolted on? |
| Craft | Does it work? Can someone else run it from your README? |
| Collaboration, shown | Your issues and board are part of the submission. We'd rather see a messy honest trail than a tidy fake one. |
| Demo | Can you make a stranger understand it in two minutes? |
Being unfinished is not disqualifying. A half-built thing with clear thinking beats a polished thing with none.
- Ideas are public to all participants. Don't submit anything you're not comfortable sharing β and don't put confidential material, credentials, or personal data in issues.
- Be generous. If someone adopts your idea, that's a compliment. Credit each other.
- Search before you submit. If your idea is close to an existing one, link it instead of duplicating β or team up.
- Ask early. Stuck on whether something fits the challenge? Ask before you build for a day.
No problem β that's genuinely part of the exercise.
- About issues
- About Projects
- Creating a project
- Filtering and grouping project views
- Linking sub-issues
- About Copilot coding agent
The example issues in this repo show what a good submission looks like β read a couple before writing your own.
.github/ISSUE_TEMPLATE/ Issue forms: idea, project submission, team task
.github/workflows/ Automation that adds new issues to the board
docs/organizer-setup.md Setup and triage notes for organizers
Questions? Open an issue or ping the organizers. Have fun. π