Update to Devpost Hackathons

{
  "name": "build-spec",
  "description": "Translate the PRD into a practical technical implementation plan.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 185
    },
    {
      "relative_path": "references/SETUP.md",
      "size_in_bytes": 1231
    },
    {
      "relative_path": "references/build-guide.md",
      "size_in_bytes": 7347
    },
    {
      "relative_path": "references/config/hackathon.json",
      "size_in_bytes": 1897
    },
    {
      "relative_path": "references/content/learning/build.md",
      "size_in_bytes": 939
    },
    {
      "relative_path": "references/content/learning/checklist.md",
      "size_in_bytes": 618
    },
    {
      "relative_path": "references/content/learning/onboard.md",
      "size_in_bytes": 1333
    },
    {
      "relative_path": "references/content/learning/prd.md",
      "size_in_bytes": 972
    },
    {
      "relative_path": "references/content/learning/scope.md",
      "size_in_bytes": 403
    },
    {
      "relative_path": "references/content/learning/spec.md",
      "size_in_bytes": 356
    },
    {
      "relative_path": "references/content/steps/check.md",
      "size_in_bytes": 1150
    },
    {
      "relative_path": "references/content/steps/help.md",
      "size_in_bytes": 2595
    },
    {
      "relative_path": "references/content/steps/map.md",
      "size_in_bytes": 948
    },
    {
      "relative_path": "references/content/steps/prepare.md",
      "size_in_bytes": 1599
    },
    {
      "relative_path": "references/content/steps/resources.md",
      "size_in_bytes": 1601
    },
    {
      "relative_path": "references/content/steps/rules.md",
      "size_in_bytes": 840
    },
    {
      "relative_path": "references/content/steps/start.md",
      "size_in_bytes": 1868
    },
    {
      "relative_path": "references/plugin-runtime.md",
      "size_in_bytes": 11707
    },
    {
      "relative_path": "references/templates/checklist-template.md",
      "size_in_bytes": 890
    },
    {
      "relative_path": "references/templates/learner-profile-template.md",
      "size_in_bytes": 394
    },
    {
      "relative_path": "references/templates/prd-template.md",
      "size_in_bytes": 298
    },
    {
      "relative_path": "references/templates/scope-template.md",
      "size_in_bytes": 245
    },
    {
      "relative_path": "references/templates/spec-template.md",
      "size_in_bytes": 294
    }
  ],
  "skill_md_contents": "---\nname: build-spec\ndescription: Translate the PRD into a practical technical implementation plan.\n---\n\n# Guided Build: Spec\n\nRead `references/build-guide.md`, then follow this command.\n\nThis is the Codex version of the learning curriculum's spec command.\n\n## Goal\n\nTurn the PRD into a technical spec detailed enough that Codex can build from it without guessing.\n\nInterview first, propose second. Adapt depth to the participant's experience level.\n\n## Preconditions\n\nRead `.devpost-hackathon-state.json`.\n\nIf the state file does not exist, direct the user to `$start-hackathon`.\n\nRead everything in `docs/hackathon-build/`. If `scope.md` or `prd.md` is missing, direct the user to the missing prior command.\n\n## Flow\n\nInterview in small batches of related questions (per the build guide). You are a technical collaborator: interview first, propose\nsecond. The participant should walk away understanding their app intimately enough to\nexplain it to someone else.\n\nMandatory beats:\n\n1. Tech preferences, calibrated to the learner profile — newer builders: \"What sounds\n   interesting to you?\" plus simple recommendations; experienced builders: \"Preferred\n   stack? Any strong opinions?\" Favor boring, reliable choices over novel plumbing —\n   winners spend their time on the product, not the infrastructure.\n2. Deployment: local only, or a deployed URL? (Running locally with screenshots is a\n   perfectly good answer.)\n3. Research the stack: rely on what you already know for well-known frameworks, libraries, and APIs; consult current official docs only for version-specific or fast-moving details you are unsure of, batching those lookups. Do not search for well-known docs you can already summarize.\n4. Propose architecture section by section, explicitly mapping PRD epics to components —\n   propose briefly, explain why, then ask for their reaction: \"Here's how I'm picturing\n   the data flow — does this match what you're thinking?\"\n5. Build the file structure and data flow together: every file and folder annotated with\n   its purpose, then walk the lifecycle of the app's most important piece of data from\n   input to storage to display.\n\nAfter mandatory beats, offer a deepening round per the build guide. Good spec deepening\ntopics: state (\"for every piece of data — where does it live, how does it get updated,\nwhat happens when they navigate away and come back?\"), exact API contracts (endpoint,\npayload, response shape — this prevents build stalls), error strategy (\"the 2-3 places\nthis will actually break during a demo\"), demo flow (\"if the coolest feature is hard to\ndemo, that's a spec problem worth solving\"), and an architecture self-review: audit your\nown draft and surface 2-3 findings as genuine questions for the participant — including\ncomplexity that doesn't match the time budget (\"this data model has six tables for an\nevening's build\").\n\n## Output\n\nUse `references/templates/spec-template.md`.\n\nCreate or update:\n\n- `docs/hackathon-build/spec.md`\n- `docs/hackathon-build/build-notes.md`\n\nCritical requirements:\n\n- every architectural component has headings\n- PRD epics are cross-referenced\n- major dependencies and APIs have documentation links\n- file structure and data flow are explicit\n- if `$build-checklist` needs to point to it, it has its own heading\n\n## State Update\n\nSet:\n\n- `learning.current_step` to `spec`\n- add `prd` to `learning.completed_steps` if missing\n- `next_command` to `build-checklist`\n\n## Presentation Output\n\nCompose the response in-context per `references/plugin-runtime.md` (\"Composing the Response\"): read `references/content/learning/spec.md`, strip maintainer `<!-- -->` comments, interpolate the event name, then present a short stage headline, the page content, and the next-step callout. Do not run any script. End by recommending `$build-checklist`.\n\n## Required References\n\n- `references/plugin-runtime.md`\n- `references/build-guide.md`\n- `references/content/learning/spec.md`\n"
}