Update to Simplified

{
  "name": "manage-projects",
  "description": "Organize marketing work in Simplified projects and project items. Use when the user asks to create or inspect a marketing project, campaign workspace, content production board, launch checklist, editorial pipeline, or deliverable list; add, retrieve, prioritize, reorder, assign, export, or remove project items; or turn an approved content plan into trackable work.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 495
    },
    {
      "relative_path": "references/project-operations.md",
      "size_in_bytes": 1818
    }
  ],
  "skill_md_contents": "---\nname: manage-projects\ndescription: Organize marketing work in Simplified projects and project items. Use when the user asks to create or inspect a marketing project, campaign workspace, content production board, launch checklist, editorial pipeline, or deliverable list; add, retrieve, prioritize, reorder, assign, export, or remove project items; or turn an approved content plan into trackable work.\n---\n\n# Manage Projects\n\nTranslate a marketing plan into accountable, sequenced work without confusing project organization with publishing authorization.\n\n## Guardrails\n\n- Inspect before mutating. Reuse an existing project when it clearly matches the user's initiative.\n- Use the same `resourcetype` for every operation on a project. Prefer `Project` for ordinary marketing work and `AdCreativeProject` only for specialized ad-creative projects.\n- Do not invent project, item, partner, or agent IDs. Resolve them from tool results or user-provided values.\n- Creating a project or item does not authorize assigning an agent, exporting content, publishing content, or deleting records.\n- Confirm the target and consequences before soft-deleting a project/item, assigning an execution agent, or exporting to a partner integration.\n- Dates must be realistic and internally ordered. Surface impossible dependencies or missing owners rather than silently compressing the plan.\n\n## Workflow\n\n1. Define the initiative: outcome, scope, deadline, deliverables, channels, approval points, owners, dependencies, and definition of done.\n2. Call `api_listProjects` with the chosen `resourcetype` and search term. Reuse a unique match or show choices when several projects could apply.\n3. If creation is requested, call `api_createProject` with a clear title, concise outcome-based description, and only supported structured data. Preserve the returned project ID.\n4. Call `api_listProjectItems` before adding work to understand existing deliverables and avoid duplicates.\n5. Convert the plan into outcome-oriented items. Each item should have one deliverable, owner or owner-needed flag, status, priority, start/due date, dependencies in the description or data, and a measurable definition of done.\n6. Call `api_createProjectItem` for authorized items. Use `data.assets` for known permanent asset UUIDs; never store signed URLs as durable references.\n7. Use `api_reorderProjectItem` only when the user requests or approves a new sequence. Use `api_assignAgentToItem` only with a resolved agent ID and explicit execution scope.\n8. Use `api_exportProjectItems` only after confirming the partner integration and exact item IDs. Report export initiation separately from export completion.\n\nRead [references/project-operations.md](references/project-operations.md) for field and lifecycle rules.\n\n## Marketing Operations Standard\n\n- Organize work around deliverables and approvals, not vague activity such as “work on social.”\n- Separate strategy, copy, creative, channel adaptation, compliance, review, scheduling, and reporting when different owners or gates apply.\n- Put the decision deadline before the publish deadline. Include contingency time for legal, customer, or executive review where relevant.\n- Use priorities to express business consequence and sequencing, not urgency theater.\n- Do not create a bloated project for a one-step request; perform the direct task unless the user wants tracking.\n\n## Output\n\nLead with project status and the critical path. Then report created or changed items, owners, dates, dependencies, approval gates, IDs needed for follow-up, and any action awaiting confirmation.\n"
}