Update to Stride AI

{
  "description": "Pick up your next Stride story: the one a teammate staged for you, or the top story assigned to you, with its acceptance criteria, designs and docs. Starts it in Stride and sets up a branch.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 43
    }
  ],
  "name": "next",
  "skill_md_contents": "---\nname: \"next\"\ndescription: \"Pick up your next Stride story: the one a teammate staged for you, or the top story assigned to you, with its acceptance criteria, designs and docs. Starts it in Stride and sets up a branch.\"\n---\n\n# Pick up the next Stride story\n\nStride is your team's delivery record. Use its MCP tools, never a guess, for\nanything about a story. Their names end in the tool name: `next_task` appears\nas `stride.next_task` or `stride_next_task`, depending on your agent.\n\nIf the user named a story key in their message, that is the story.\n\n1. **Find the story.**\n   - If the user named a story (a ticket key such as `ORB-526`), call\n     `get_story_context` with that key.\n   - Otherwise call `next_task`. It returns the story a teammate staged for\n     you with \"Hand to your agent\" or, when nothing is staged, the top\n     unstarted story assigned to the user (the active sprint first, then by\n     priority), with its full context in the same call.\n   - If there is nothing to work on, say so and stop. Suggest staging a\n     story from its \"Hand to your agent\" panel in Stride, or assigning one to\n     themselves, and running `$stride:next` again.\n   - If Stride's tools are missing, or answer that the request is not\n     authorized, the user needs to sign in to Stride. Ask them to open Stride AI in Plugins (`/plugins` in Codex CLI, or Plugins in ChatGPT) and connect it when prompted. A browser window opens to sign in to Stride.\n2. **Brief the user** in a few lines: the key and title, the goal in a\n   sentence or two, every acceptance criterion as a numbered list, and\n   whatever is linked that changes the work (designs, documents, blocking or\n   related stories, open defects).\n3. **Start it in Stride.** If the story is still to do, call\n   `update_story_status` with the key, status `IN_PROGRESS`, and a one-line\n   comment that you have picked it up. Leave a story that is already in\n   progress or further along where it is. If Stride reports a conflict\n   because a person edited the story, read it again with `get_story` and\n   retry once. Never pass `force` unless the user explicitly tells you to\n   overwrite their teammate's edit.\n4. **Set up the work.** In a git repository, create and switch to a branch\n   named after the key and title, such as `orb-526-export-csv`, unless the\n   user is already on a branch for this story. Never discard, reset or stash\n   uncommitted work without asking.\n5. **Implement it** against the acceptance criteria, keeping the user in the\n   loop. When it is done, suggest `$stride:done` to check the work and hand it back\n   for review.\n"
}