Update to Meetly

{
  "name": "create-meetly-product-spec",
  "description": "Create an evidence-grounded product brief, PRD, or engineering specification from an authorized Meetly product, customer, design, or technical discussion.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 531
    }
  ],
  "skill_md_contents": "---\nname: create-meetly-product-spec\ndescription: Create an evidence-grounded product brief, PRD, or engineering specification from an authorized Meetly product, customer, design, or technical discussion.\n---\n\n# Create a Meetly Product Spec\n\nUse `search` and `fetch` to retrieve the relevant meeting evidence. Use\n`get_transcript` only when exact wording or a bounded missing passage matters.\n\nChoose the lightest artifact that fits the user's goal:\n\n- Product brief for discovery and alignment.\n- PRD for agreed product behavior and measurable outcomes.\n- Engineering specification for implementation decisions and interfaces.\n\nReorganize the discussion for the team that must decide or build, rather than\nfollowing transcript order. Cover context, problem, users, goals, non-goals,\nrequirements, success measures, constraints, decisions, rejected options, risks,\nand open questions as applicable. Engineering specs should also cover system\ncontext, data and interface changes, edge cases, security/privacy, rollout,\nobservability, and testing.\n\nRequirements must be testable. Preserve speaker labels and attach concise quotes\nor timestamped evidence to material claims. Mark host inference explicitly.\nNever invent approvals, dates, owners, or technical constraints; surface\ncontradictions and missing decisions.\n\nCreate the document directly with the host's native document or coding\ncapabilities. Do not look for a Meetly prepare, render, HTML, or document tool.\n"
}