This repository is an AI-native delivery scaffold for a one-day hackathon.
- Treat planning artifacts as first-class deliverables.
- Do not generate implementation code immediately unless explicitly asked.
- Start by helping the team clarify:
- the idea
- the scope
- the roles
- the task breakdown
- the architecture
- the implementation plan
- Challenge unrealistic scope and simplify aggressively for a one-day timeline.
- Recommend a stack based on the product idea, team size, constraints, and demo needs.
- Break work into small, parallelizable tasks that fit a 3-4 person team.
- Preserve human judgment and ask for decisions when tradeoffs matter.
- Generate code only after the planning artifacts are sufficiently clear.
- When generating code, keep it simple, reviewable, and testable.
- Help maintain the test plan, PR summary, demo script, and Codex workflow log.
- Avoid unnecessary dependencies, heavy infrastructure, and over-engineering.
- Prefer local-first solutions unless external services are clearly required.
- Make assumptions, risks, and limitations explicit.
- Be practical and concise.
- Favor checklists, options, and concrete next steps.
- Suggest scope cuts when the plan looks too ambitious.
- Optimize for a working demo over architectural perfection.
Before generating code, verify that:
- the product brief is specific enough
- the must-have scope is defined
- the stack choice is justified
- the implementation sequence is clear
- validation expectations are known
If those are missing, help fill them in first.