Compass

Dashboard

Inspiration

We were inspired by the way teams often lose track of important tasks inside long Slack threads, GitHub issues, and fast-moving project conversations. During a hackathon, this problem becomes even more obvious: there are limited hours, many things to build, and not enough time to manually decide who should do what.

What it does

The system takes in project context, identifies what needs to be done, breaks the work into actionable steps, and recommends an owner or reviewer based on their skills and fit for the task. Compass is designed to help teams move faster by reducing the time spent deciding how to approach work and who should handle it.

How we built it

Frontend: Built with Figma, allowing us to map out the workflow clearly. We then used Claude and Codex to turn the Figma flow into a working frontend. Backend: We used the sponsors Nexla, Zero.xyz, and Pomethium. Nexla is our data layer which links context for our loop, so that it can suggest issues to the best suited employees. Zero.xyz is used to suggest potential api tools during the planning stage. Pomethium is used the maintain application security.

Challenges we ran into

On the backend, some challenges we ran into were issues with branches getting lost and mixed up. When working on the frontend, the biggest issue we ran into was reiterating the design multiple times.

Accomplishments that we're proud of

Creating a working product within the limited five-hour time frame was something we were proud of. We also developed the idea quickly and on the fly within the first hour of the hackathon.

What we learned

We learned how to optimize our time given a hard deadline and a small time frame.
We learned how to allocate work practically.
Finally, we learned how valuable fast iteration is. Whether it was improving the frontend design, fixing branch issues, or refining the product idea, we had to keep adjusting quickly and moving forward. ## What's next for Compass Next, we want Compass to integrate more deeply with tools like Slack, GitHub, Jira, and Linear so it can understand real team conversations, issues, and pull requests. We also want to improve the task-matching system so Compass can recommend employees based on skills, workload, past contributions, and availability. In the future, Compass