Manage execution stages and tasks — list, add, edit, delete, and create tickets for tasks.
Always prefix active workspace, project, or ticket names with a 🟢 emoji.
Follow these steps in order.
Read .duplocloud/state.toon and .env.
Capture workspace_id, project_id, project_name if present.
Case A: Project is already active (project_id present in state)
activate_project flow.Case B: No active project (project_id absent)
Call duplo-helpdesk::Workspaces_get_available to get available workspaces.
If no workspaces, tell the user:
"No workspaces available. Please create one in the DuploCloud portal first." Then stop.
If only one workspace, auto-select and capture its id as workspace_id. Tell the user:
"Auto-selecting 🟢 <workspace name> — it's the only workspace available."
If multiple workspaces, show a numbered list and ask: "Which workspace?"
Capture the selected workspace's id as workspace_id.
Call duplo-helpdesk::Projects_list with workspaceId = workspace_id.
If no projects, tell the user:
"No projects found in this workspace. Please create one in the DuploCloud portal first." Then stop.
Filter projects to those with execution stages:
duplo-helpdesk::Projects_get with id = <each project>.execution.stages is non-empty and has at least one stage with tasks.If no projects with execution stages, tell the user:
"No projects with execution stages found. Please run
/duplo:ai_planneron a project to generate stages and tasks first." Then stop.
Show a numbered list of projects with execution stages (name and task count):
Projects with execution stages:
1. <name> — <N> total tasks
2. ...Ask: "Which project would you like to work on?"
Capture the selected project's id as project_id and name as project_name.
Call duplo-helpdesk::Projects_get with id = project_id.
Extract and store:
execution.stages → stagesexecution.version → execution_versionCall duplo-helpdesk::Ticket_list with workspaceId = workspace_id.
From the returned tickets, build task_ticket_map keyed by metadata.taskId using only tickets where all of the following are true:
originContext.type is ProjectoriginContext.id equals project_idoriginContext.metadata.projectType equals plan_executionoriginContext.metadata.taskId is presentFor each mapped ticket, capture:
ticket_nameticket_titleticket_statusIf stages is empty or absent, tell the user:
"No execution stages found for 🟢 <project_name>. Please generate execution stages first using
/duplo:ai_planner." Then stop.
Save state silently:
workspace_id: <workspace_id>
project_id: <project_id>
project_name: <project_name>Proceed to Step 1.
Display:
Project: 🟢 <project_name>
Execution Stages:
1. <stage.title> — <stage.description> (<N> tasks)
2. ...Ask: "Which stage would you like to work on? (number, or 'done')"
active_stage (with name, title, description, and full tasks array where each task has name, title, description, version). Proceed to Step 2.Display the stage description in a hard frame:
╔═══════════════════════════════════════════════════════╗
║ Stage: 🟢 <active_stage.title> ║
╠═══════════════════════════════════════════════════════╣
║ <active_stage.description> ║
╚═══════════════════════════════════════════════════════╝Ask:
"What would you like to do with this stage?
- Edit stage name / description
- Add a new task
- Manage a task
- Back to stage list
- Done"
Tell the user the current values:
"Current name: <active_stage.title>
Current description: <active_stage.description>"
Ask: "New name? (press Enter to keep current)" Ask: "New description? (press Enter to keep current)"
Apply only the values the user provided. Keep unchanged fields as-is.
Re-fetch the project: call duplo-helpdesk::Projects_get with id = project_id. Update execution_version and re-capture active_stage tasks.
Call duplo-helpdesk::Projects_update_plan_execution with id = project_id and body:
{
"version": "<execution_version>",
"stageToAddOrUpdate": [
{
"name": "<active_stage.name>",
"title": "<updated title>",
"description": "<updated description>",
"tasksToAddOrUpdate": [
{ "name": "<task.name>", "title": "<task.title>", "description": "<task.description>", "version": "<task.version>" }
]
}
]
}Tell the user: "Stage updated." Go back to Step 2.
Ask: "Task title:" Ask: "Task description:"
Generate a UUID:
python3 -c "import uuid; print(uuid.uuid4())"Capture as new_task_id.
Re-fetch the project: call duplo-helpdesk::Projects_get with id = project_id. Update execution_version and re-capture current tasks for active_stage.
Build tasksToAddOrUpdate: all existing tasks (with name, title, description, version) plus the new entry:
{ "name": "<new_task_id>", "title": "<user title>", "description": "<user description>" }Call duplo-helpdesk::Projects_update_plan_execution with id = project_id and body:
{
"version": "<execution_version>",
"stageToAddOrUpdate": [
{
"name": "<active_stage.name>",
"title": "<active_stage.title>",
"description": "<active_stage.description>",
"tasksToAddOrUpdate": [ ...existing tasks..., { "name": "<new_task_id>", "title": "<title>", "description": "<description>" } ]
}
]
}Tell the user: "Task <title> added." Go back to Step 2.
For each task in active_stage.tasks, look up an existing linked ticket in task_ticket_map using task.name.
Display:
Tasks in <active_stage.title>:
1. <task.title> — 🟢 Ticket: <ticket_title> (<status>)
2. <task.title> — No ticket
...Ask: "Which task? (number, or 'back')"
active_task (with name, title, description, version) and task_ticket_name / task_ticket_status if a ticket was found. Proceed to Step 5a.Whenever the project is re-fetched later in this flow, also refresh task_ticket_map from Ticket_list before showing task menus again.
Ask:
"What would you like to do with task 🟢 <active_task.title>?
- Create ticket for this task
- Move to a different stage
- Edit name / description
- Delete task
- Back to task list"
Block rule: If the task already has a ticket with status open, inProgress, or closed, tell the user:
"This task already has a ticket <ticket_title> (<status>). A new ticket cannot be created." Go back to Step 5a.
If no ticket exists, or the existing ticket has status resolved or cancelled: proceed.
Delegate to skills/task_ticket/SKILL.md:
workspace_id, project_id, active_task (with name, title, description), and active_stage.After task_ticket returns (ticket created), go back to Step 5.
Re-fetch the project: call duplo-helpdesk::Projects_get with id = project_id. Update stages and execution_version.
List the other stages (exclude active_stage):
Move to which stage? (or 'back' to cancel)
1. <stage.title>
2. ...
N. BackWait for selection:
target_stage (with name, title, description, tasks).Remove from current stage: Build tasksToAddOrUpdate for active_stage containing all tasks except active_task.
Add to target stage: Build tasksToAddOrUpdate for target_stage containing all its current tasks plus active_task (without version field for the moved task).
Call duplo-helpdesk::Projects_update_plan_execution with id = project_id and body:
{
"version": "<execution_version>",
"stageToAddOrUpdate": [
{
"name": "<active_stage.name>",
"title": "<active_stage.title>",
"description": "<active_stage.description>",
"tasksToAddOrUpdate": [ ...all tasks except active_task... ]
},
{
"name": "<target_stage.name>",
"title": "<target_stage.title>",
"description": "<target_stage.description>",
"tasksToAddOrUpdate": [ ...target stage tasks..., { "name": "<active_task.name>", "title": "<active_task.title>", "description": "<active_task.description>" } ]
}
]
}Tell the user: "Task <active_task.title> moved to stage <target_stage.title>." Go back to Step 5.
Tell the user the current values:
"Current name: <active_task.title>
Current description: <active_task.description>"
Ask: "New name? (press Enter to keep current)" Ask: "New description? (press Enter to keep current)"
Apply only provided values.
Re-fetch the project: call duplo-helpdesk::Projects_get with id = project_id. Update execution_version and re-capture all tasks for active_stage.
Build tasksToAddOrUpdate: all tasks for active_stage, replacing active_task with the updated values.
Call duplo-helpdesk::Projects_update_plan_execution with id = project_id and body:
{
"version": "<execution_version>",
"stageToAddOrUpdate": [
{
"name": "<active_stage.name>",
"title": "<active_stage.title>",
"description": "<active_stage.description>",
"tasksToAddOrUpdate": [ ...all tasks with active_task updated... ]
}
]
}Tell the user: "Task updated." Update active_task with the new values. Go back to Step 5a.
Ask for confirmation:
"Are you sure you want to delete task <active_task.title>? This cannot be undone. (y/n)"
Re-fetch the project: call duplo-helpdesk::Projects_get with id = project_id. Update execution_version and re-capture tasks for active_stage.
Build tasksToAddOrUpdate: all tasks for active_stage except active_task.
Call duplo-helpdesk::Projects_update_plan_execution with id = project_id and body:
{
"version": "<execution_version>",
"stageToAddOrUpdate": [
{
"name": "<active_stage.name>",
"title": "<active_stage.title>",
"description": "<active_stage.description>",
"tasksToAddOrUpdate": [ ...all tasks except active_task... ]
}
]
}Tell the user: "Task <active_task.title> deleted." Go back to Step 5.
duplocloud/duplo-claude-plugin
6a46510
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.