Update to Devpost Hackathons

{
  "description": "Start the optional guided build tool inside Step 3 Resources. Use when the participant wants help shaping a hackathon project before submission prep.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 193
    },
    {
      "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": 1136
    },
    {
      "relative_path": "references/content/steps/start.md",
      "size_in_bytes": 1868
    },
    {
      "relative_path": "references/plugin-runtime.md",
      "size_in_bytes": 11790
    },
    {
      "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
    }
  ],
  "name": "build-onboard",
  "skill_md_contents": "---\nname: build-onboard\ndescription: Start the optional guided build tool inside Step 3 Resources. Use when the participant wants help shaping a hackathon project before submission prep.\n---\n\n# Guided Build: Ideate\n\nRead `references/build-guide.md`, then follow this command.\n\nThis is the Codex version of the learning curriculum's onboarding command. In the participant UI, this phase is labeled `Ideate`.\n\n## Goal\n\nWelcome the participant, introduce the optional guided path, begin brainstorming the project idea, and create `docs/hackathon-build/learner-profile.md` so every downstream build command can calibrate to who they are.\n\nDo not over-explain the whole process. Keep onboarding warm and efficient.\n\n## Preconditions\n\nRead `.devpost-hackathon-state.json`.\n\nIf the state file does not exist, direct the user to `$start-hackathon`.\n\nIf `rules_acknowledged` is not `true`, direct the user to `$review-hackathon-rules` first.\n\nCreate `docs/hackathon-build/` if needed. Read any existing files in it before asking questions.\n\n## Flow\n\nOpen with a brief welcome. Make one thing explicit up front: this is THEIR project — the\nbest outcomes come when they actively shape every step, push back on suggestions, and say\nwhen something doesn't feel right. Then explain:\n\n- **the opening bookend — set expectations honestly:** this will help you get to a proof\n  of concept. It will not finish the thing for you — you'll keep working on it after. And\n  if you're newer to coding with AI, it's a good way to get practice with the more\n  structured best practices of doing it. (`$build-project` closes this bookend at the end\n  of the build — the promise made here is the one kept there.)\n- the format: this works like an interview — Codex asks, you talk, Codex writes the docs.\n  The more context you give, the better everything downstream gets.\n- answering by voice works great here: use your operating system's built-in dictation, a\n  third-party speech-to-text app — or, in the desktop app, click the microphone icon in\n  the input bar. Longer, rambling answers are exactly the right material. Summarize\n  dictated answers back and confirm before writing durable files.\n- the docs are useful build context and submission evidence\n- the command chain is `$build-onboard -> $build-scope -> $build-prd -> $build-spec -> $build-checklist -> $build-project`\n\nThe composed onboard page (`references/content/learning/onboard.md`) carries the bookend, the\nvoice note, and the token-strategy tip (plan with your most powerful model, execute with\ncheaper models or subagents) — let the page say them and keep your own welcome prose to a\nline or two; do not deliver the same pitch twice in one response.\n\nKeep the onboarding brisk. Ask questions in batches, not one at a time — repeated single-question back-and-forth is cumbersome in the desktop app.\n\n**Name — never ask for it.** Call `devpost.whoami` once during this onboarding (the sanctioned personalization exception in `references/plugin-runtime.md`) and greet the participant by the name it returns, confirming in passing (\"I'll call you Joe — say otherwise if you'd prefer something else\"). If the call fails or returns no usable name, simply proceed without one — do not ask for a name, do not mention the miss, do not treat it as an error. Do not ask what brought them to the hackathon.\n\nThe interview runs in rounds:\n\n**Round 1 — the essentials.** One message, these two questions:\n\n1. Do you have an idea of what you want to build today? (A rough sketch is fine — \"no idea yet\" is a valid answer.)\n2. What's your coding experience — level, and any languages, frameworks, or AI coding agents you've used?\n\n**Round 2 — sharpen the idea (always runs).** One batched message of 3-4 questions reacting to their round-1 answers: draw on **Sharpening Questions** in the build guide to make the idea concrete, or — if they had no idea yet — brainstorm with them until a candidate direction emerges. Do not skip this round or offer to skip it; the extra context is the point.\n\n**Round 3 — the fun round (optional per question).** Offer a menu of 4-6 lighter questions and say explicitly: **answer any of these that spark something — skip the rest freely.** Draw from:\n\n- inspirations: movies, games, apps, other software — anything whose spirit they'd like this project to have\n- look and feel: color palettes, fonts, design tokens, aesthetic styles\n- tone and vibe, asked creatively — e.g. \"If your app were a place, what would it feel like to walk into?\" or \"What's an app whose *feel* you'd steal, even if it does something totally different?\"\n\nAfter round 3 (answered or skipped), move on to `$build-scope`.\n\n## Output\n\nUse `references/templates/learner-profile-template.md`.\n\nCreate or update:\n\n- `docs/hackathon-build/learner-profile.md`\n- `docs/hackathon-build/build-notes.md`\n\n## State Update\n\nSet:\n\n- `learning.status` to `active`\n- `learning.current_step` to `onboard`\n- add `resources` to `completed_stages` if missing\n- `current_stage` to `resources`\n- `next_command` to `build-scope`\n- `participant.display_name` when `whoami` returned a name the participant didn't correct, or they gave a preferred one\n- `project.summary` when the participant describes the project idea\n- `project.name` when the participant gives a clear project name\n\n## Presentation Output\n\nCompose the response in-context per `references/plugin-runtime.md` (\"Composing the Response\"): read `references/content/learning/onboard.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 with a compact note that the next command is `$build-scope`.\n\n## Required References\n\n- `references/plugin-runtime.md`\n- `references/build-guide.md`\n- `references/content/learning/onboard.md`\n"
}