🚀 About the Hackathon
Join us on Saturday, January 31st for the Prompt Driven Development (PDD) Hackathon, hosted by PromptDriven.ai and Toolhouse at the 500 Global offices in Palo Alto.
This isn't just another hackathon — it's an introduction to a new paradigm of software creation. You will leverage Prompt Driven Development and Toolhouse.ai to build agentic applications that can take real-world actions. Whether you are a student, a seasoned developer, or a founder, come prepared to shift from writing code to orchestrating intelligence.
🏆 The Challenge
Build a project using the PDD approach and/or Toolhouse.ai
- Master PDD: Learn to use AI agents to automate the prototyping lifecycle
- Build with Toolhouse: Give your LLMs the ability to use tools and interact with the internet
- Ship Fast: Go from idea to working demo in a single day
Also register on Luma: https://luma.com/nocpgiou
Please view Rules page for eligibility information
Requirements
What to Build
Build an AI-Powered Application Using Prompt-Driven Development
Create a project that demonstrates the power of Prompt-Driven Development (PDD) - where prompts are the source of truth and code is a regenerable artifact.
Eligible Project Types
Agentic Applications
-
AI agents that take real-world actions via Toolhouse
-
Automated workflows that interact with external APIs and services
-
Multi-step task automation with LLM-powered decision making
Developer Tools
-
Tools that enhance the PDD workflow
-
Code generation utilities that follow PDD principles
-
Testing frameworks that support test accumulation
Enterprise Solutions
-
Business process automation using prompt-defined logic
-
Customer-facing AI applications with maintainable architecture
-
Data processing pipelines defined by regenerable prompts
Creative Applications
-
Interactive applications powered by AI agents
-
Content generation tools with structured prompt workflows
-
Educational platforms leveraging LLM capabilities
Required Technologies
Prompt-Driven Development (PDD) - Your project must demonstrate PDD principles:
-
Prompts define behavior; code is generated
-
Changes made by modifying prompts and regenerating (not patching)
-
Intent preserved in prompts, not buried in code
Toolhouse.ai (Recommended) - Give your LLMs the ability to:
-
Use tools and interact with the internet
-
Execute real-world actions
-
Access external services and APIs
Rtrvr.ai (Recommended) - Visit Resources for more information
ElevenLabs (Recommended) - Visit Resources for more information
Why PDD?
From the PDD whitepaper benchmarks:
-
55% reduction in active developer time vs. interactive patching
-
100% success rate in complex tasks vs. 46.67% for traditional approaches
-
10x lower cost per successful operation ($0.08 vs $0.77)
PDD treats prompts like molds in manufacturing - invest in the specification once, regenerate the artifact as needed. Your tests become "mold walls" that permanently prevent bugs from recurring.
What to Submit
Required Submissions
Project Repository
-
Public GitHub/GitLab repository with your code
-
Must include a /prompts directory containing your PDD prompts
-
README with setup instructions
Demo Video (3-5 minutes)
-
Show your application in action
-
Explain how you used PDD methodology
-
Highlight Toolhouse.ai integration (if used)
Pitch Deck (5-10 slides)
-
Problem statement and market opportunity
-
Solution overview and technical approach
-
Business model and go-to-market strategy
-
Team background
PDD Artifacts
-
At least one module with:
-
Prompt file (.prompt)
-
Generated code
-
Usage example
-
Test file
-
Demonstrate the regeneration workflow
Submission Checklist
|
Working application deployed or runnable locally |
|
Source code with PDD prompt files |
|
Demo video uploaded to YouTube/Vimeo |
|
Pitch deck (PDF or link to slides) |
|
Project description on Devpost |
|
Team member information |
Bonus Points
-
Multiple modules using PDD methodology
-
Evidence of test accumulation (tests preserved across regenerations)
-
Integration with PDD Cloud for grounding/few-shot examples
-
Clear documentation of the prompt-to-code relationship
Prizes
Grand Prize: VC Pitch Opportunity
- Direct pitch session with 500 Global, AI Sprouts, Workplay Ventures, Blitzscaling Ventures, and FalconX Ventures
- Mentorship session with Clayton Bryan (500 Global Partner)
- PDD Cloud credits ($500)
- Toolhouse.ai credits ($500)
Runner-Up Prize: Best Technical Implementation
- PDD Cloud credits ($250)
- Toolhouse.ai credits ($250)
- Featured case study on PDD website
Runner-Up Prize: Most Innovative Use Case
- PDD Cloud credits ($250)
- Toolhouse.ai credits ($250)
- Opportunity to present at future PDD community event
Runner-Up Prize: Best Enterprise Application
- PDD Cloud credits ($250)
- Toolhouse.ai credits ($250)
- Introduction to enterprise pilot program
- Technical advisory session
Best Project Built with ElevenLabs
Each team member receives 6 months of ElevenLabs Scale tier ($330/month, $1,980 total value per person)
Special Honorable Mention
- PDD Cloud credits ($250)
- Toolhouse.ai credits ($250)
- Direct pitch session with VCs.
Devpost Achievements
Submitting to this hackathon could earn you:
Judges
Clayton Bryan
Investor, 500 Global
Chris Yeh
General Partner, Blitzscaling Ventures
Suman Talukdar
Investor, AI Sprouts
Angad Randhawa
FalconX / VentureDock
Shaurya Mehta
Investor, Workplay Ventures
Judging Criteria
-
Primary Criteria (100 points total)
-
Innovation & Originality (25 points)
Does the project demonstrate a novel application of Prompt-Driven Development? Is the approach creative in solving a real problem? Does it push the boundaries of what's possible with AI-assisted development? -
Technical Implementation (25 points)
Is the project built using PDD methodology (prompts as source of truth)? Does it leverage Toolhouse.ai effectively for agent capabilities? Is the code regenerable from prompts rather than patched incrementally? -
Investment Potential (25 points)
Is there a clear market need and business model? Does the solution have scalable architecture? Can the team articulate a path to revenue? -
Presentation & Demo (15 points)
Is the pitch compelling and well-structured? Does the demo clearly show the value proposition? Can the team effectively communicate the technical approach? -
Use of PDD Principles (10 points)
Prompts as source of truth (not ephemeral chat instructions) Regenerative development (modify prompt, regenerate code) Test accumulation (tests preserved across regenerations) Synchronization (prompts, code, examples, and tests stay aligned)
Questions? Email the hackathon manager
Tell your friends
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.




