Update to Creative Production

{
  "name": "intake",
  "description": "Use when Creative Production is explicitly invoked or mentioned without a concrete request, when the user asks what Creative Production can do, or when the user wants help getting started without enough context to choose a workflow.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 215
    }
  ],
  "skill_md_contents": "---\nname: intake\ndescription: Use when Creative Production is explicitly invoked or mentioned without a concrete request, when the user asks what Creative Production can do, or when the user wants help getting started without enough context to choose a workflow.\n---\n\n# Intake\n\nOpen the Creative Production app in its zero state.\n\nThis skill owns the no-brief entry point. It does not generate images, choose a production mode, or ask structured questions.\n\n## Workflow\n\n1. Call `creative_production_board` exactly once with:\n\n```json\n{\n  \"action\": \"open\",\n  \"title\": \"Creative Production\",\n  \"summary\": \"Start with an idea\"\n}\n```\n\n   Preserve the returned `boardId`; it is the only target for later actions.\n2. Let the app show its starter grid.\n3. Do not ask a chat question before the app appears.\n4. Do not call any structured intake tool.\n5. When the user selects a starter, let the app open an editable follow-up prompt. Opening the prompt must not create a placeholder.\n6. After submission, hand off to `produce` with the existing `boardId`. Call `begin_generation` only when generation actually starts, then call `complete_generation` for each generated file. Never call `open` again for that workflow.\n\n## Exit\n\nStop after the zero-state app is visible. The next user turn or starter follow-up owns the concrete creative request and updates this same board.\n"
}