Projects and items

These commands manage creative projects and their items. Dedicated PM boards—columns, task assignees, subtasks, and dependencies—are a separate capability and have no dedicated commands in CLI 1.8.0. Even a project routing value named pm does not expose the PM-board API.

Projects group related work. Project items represent the deliverables inside a project. The CLI can create and inspect both, assign an existing agent to an item, change its position, and export selected items to a partner integration.

1. Choose the project type

Every project command needs --type, which selects the kind of project you are working with. Common values include pm, blogger, ad, campaign, and blog. Specialized content types include SMQuotes, AIAvatarVideo, AiProductVideos, UGCVideo, and ImageYTThumb. Type names are case-sensitive.

Use the same type when listing a project and working with its items. These commands manage content projects and items; do not assume they expose every board-management operation available elsewhere in Simplified.

2. Find or create a project

simplified projects:list --type pm
simplified projects:create --type pm --title "Autumn launch" \
  --description "Campaign deliverables for the autumn collection."

Copy the returned project ID:

simplified projects:get --type pm --id "PROJECT_ID"

Use --search, --ordering, or --primary-type with projects:list to narrow the result set. --type chooses the resource; --primary-type is an additional category filter.

3. Add a deliverable

simplified projects:item-create --type pm --project "PROJECT_ID" \
  --title "Write the launch announcement" \
  --description "Prepare the first draft using the approved brand voice." \
  --status todo

Items can also include --start-date and --due-date in ISO 8601 format, a numeric --priority, and structured --data. Use status values appropriate to your workflow. The CLI accepts a status string; it does not discover a board’s status choices for you.

List the project items and copy the new item’s ID:

simplified projects:item-list --type pm --project "PROJECT_ID"
simplified projects:item-get --type pm --project "PROJECT_ID" --id "ITEM_ID"

4. Assign an existing agent

When an agent is available for this work, use its UUID:

simplified projects:item-assign-agent --type pm --project "PROJECT_ID" \
  --id "ITEM_ID" --agent-id "AGENT_UUID"

This command assigns an agent to an item; it does not create an agent. Retrieve the item again to inspect the assignment and follow its execution in Simplified.

5. Order and export deliverables

Move an item to a new position index:

simplified projects:item-reorder --type pm --project "PROJECT_ID" \
  --id "ITEM_ID" --position 0

Export selected items to a configured partner integration:

simplified projects:export --type pm --project "PROJECT_ID" \
  --partner-id 42 --item-ids "ITEM_ID_1,ITEM_ID_2"

Replace 42 with the actual partner integration ID. Exporting sends items to that integration; check both the selected IDs and destination before running it.

Use a file for richer input

projects:create and projects:item-create accept --json for a complete request body. Use --data for the resource’s nested data object. The full body and nested data are not interchangeable. Required routing flags such as --type and --project remain necessary when reading a body from a file.

Remove an item or project

simplified projects:item-delete --type pm --project "PROJECT_ID" --id "ITEM_ID"
simplified projects:delete --type pm --id "PROJECT_ID"

These commands soft-delete the selected resource. Inspect the project or item first so you are acting on the intended deliverable.