Update to Simplified for AI

{
  "description": "Organize creative marketing projects and their deliverable items in Simplified, including collections, ordering, asset handoffs, assignments, and exports. Use for marketing project/item records. Kanban boards, tasks, subtasks, statuses, and native dependencies are not handled here; they need the simplified-project-management skill and the full connector, where available.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 495
    },
    {
      "relative_path": "references/project-operations.md",
      "size_in_bytes": 3523
    }
  ],
  "name": "manage-projects",
  "skill_md_contents": "---\nname: manage-projects\ndescription: Organize creative marketing projects and their deliverable items in Simplified, including collections, ordering, asset handoffs, assignments, and exports. Use for marketing project/item records. Kanban boards, tasks, subtasks, statuses, and native dependencies are not handled here; they need the simplified-project-management skill and the full connector, where available.\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- Resolve the exact target and consequences before soft-deleting, assigning an execution agent, or exporting. A user request that specifies the action and scope is authorization; ask only when the target, destination, or execution scope is unclear.\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. Resolve named or uncertain workspace/teamspace scope with `simplified-workspace` and carry numeric `space_id` on every call. Kanban boards, team task ownership, subtasks, and native dependencies are a different resource served only by the full connector (`simplified-project-management`, where installed); if it is not available, say so rather than approximating with project items. Call `api_listProjects` with the chosen `resourcetype` and `search`. Reuse a verified unique match or show choices when several projects could apply. `expand: \"items\"` can include deliverables and avoid separate listings.\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. Inspect the returned items, or call `api_listProjectItems` on an existing project, before adding work to avoid duplicates. A newly created empty project does not need another inventory call.\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. Revise existing work with `api_updateProject` or `api_updateProjectItem`; read first and send the complete merged `data` object when changing it. Use `api_reorderProjectItem` within the requested organization scope. Use `api_assignAgentToItem` only with a resolved agent UUID and authorized execution scope; Resolve agents through the separately configured automation/full connection when enabled; follow `simplified-workflows` for discovery and capability checks. Assignment alone does not establish completion.\n8. Use `api_exportProjectItems` with the resolved numeric `partner_id` and exact `item_ids` within the authorized destination scope. There is no dedicated partner-discovery tool in the current public schema; use a known configured ID or verified supported discovery, and ask when the destination is unresolved. Report export initiation separately from 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"
}