Hedera Hackathon PRD
Hedera Hackathon PRD Generator
Generate a comprehensive PRD for a Hedera hackathon project, structured to maximize scores across all 7 judging criteria: Innovation (10%), Feasibility (10%), Execution (20%), Integration (15%), Validation (15%), Success (20%), and Pitch (10%).
Step 1: Gather Bounty / Track Context
Before asking any other questions, ask the participant to paste the bounty or track description they are targeting. This is critical for tailoring the PRD to what judges are specifically looking for.
Prompt them with:
Before we start, please paste the full description of the bounty or track you're submitting to. This includes the track name, description, requirements, prize details, and any specific evaluation criteria. The more context you share, the better I can tailor your PRD to what the judges are looking for.
If you're targeting multiple tracks, paste all of them.
Once the participant provides the bounty/track context:
- Identify specific requirements, themes, or technologies mentioned in the track
- Note any track-specific evaluation criteria beyond the standard judging rubric
- Look for preferred Hedera services, partner integrations, or use cases called out in the track
- Use this context to inform all subsequent questions and the generated PRD
More from hedera-dev/hedera-skills
hedera plugin creation
This skill should be used when the user asks to "create a hedera plugin", "build a hedera agent kit plugin", "extend hedera agent kit", "create custom hedera tools", "add hedera functionality", "write a hedera tool", "implement hedera tool", or needs guidance on Hedera Agent Kit plugin architecture, tool definitions, mutation tools, query tools, or parameter schemas using Zod.
36hts system contract skill
Hedera Token Service (HTS) smart contract development. Use when creating, managing, or interacting with Hedera-native tokens via Solidity contracts. Triggers include HTS tokens, Hedera token creation, HTS precompile, token minting/burning on Hedera, KYC/freeze/pause token controls, custom fee schedules, NFT collections on Hedera, or any token operations using the 0x167 precompile.
36hedera hackathon submission validator
This skill should be used when the user wants to validate, review, or score their Hedera hackathon submission before submitting. Triggered by phrases like "validate hackathon submission", "review my hackathon project", "hackathon scorecard", "check submission readiness", "score my hackathon", "submission review", "judge my project", "hackathon submission quality", or "improve hackathon score".
34hedera-token-service
How to create, manage, and transfer tokens on Hedera using the Hiero JavaScript SDK (@hiero-ledger/sdk). Use this skill whenever the user wants to work with fungible tokens, NFTs, token creation, minting, burning, transfers, token association, custom fees (fixed, fractional, royalty), airdrops, KYC/freeze/wipe/pause operations, or any HTS (Hedera Token Service) operation in JavaScript or TypeScript. Also trigger when users mention @hashgraph/sdk token operations, ERC-20/ERC-721 equivalents on Hedera, or tokenization on the Hedera network.
26hedera-consensus-service
How to create topics, submit messages, and subscribe to real-time message streams on Hedera using the Hiero JavaScript SDK (@hiero-ledger/sdk). Use this skill whenever the user wants to work with Hedera Consensus Service (HCS), including topic creation, message submission, pub/sub messaging, mirror node subscriptions, chunked large messages, topic fees, or any consensus-related operation in JavaScript or TypeScript. Also trigger when users mention @hashgraph/sdk topic operations, event logging on Hedera, decentralized messaging, audit trails, or ordered message streams.
23schedule service system contract skill
Hedera Schedule Service (HSS) smart contract development. Use when creating or interacting with scheduled transactions from Solidity via the Schedule Service system contract at 0x16b (e.g. scheduleNative for token creation, scheduleCall for generalized contract calls, authorizeSchedule, signSchedule, deleteSchedule, or querying scheduled token info).
21