Add a new execution task to a stage in the active project.
This skill delegates to skills/stage_tasks/SKILL.md.
Read and follow skills/stage_tasks/SKILL.md:
activate_project): Follow Steps 0–0b to select a workspace/project with execution stages, then continue.activate_project: The project is already active, so Step 0a (project selection) is skipped — go directly to Step 0b (load data).stage_tasks flow or stop.Always prefix active workspace, project, or ticket names with a 🟢 emoji.
Follow these steps in order.
Read .duplocloud/state.toon and .env.
project_id or workspace_id is absent: tell the user:
"No active project. Please run
/duplo:activate_projectfirst." Then stop.
Capture project_id, project_name, workspace_id, DUPLO_TOKEN, DUPLO_HELPDESK_URL.
Call duplo-helpdesk::Projects_get with id = project_id.
Extract:
execution.stages → stagesexecution.version → execution_versionIf 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.
Display:
Project: 🟢 <project_name>
Execution Stages:
1. <stage.title> — <stage.description> (<N> tasks)
2. ...Ask: "Which stage would you like to add a task to? (number)"
Capture the selected stage as active_stage (with name, title, description, and full tasks array including each task's name, title, description, version).
Ask: "What is the title of the new task?"
Wait for response. Capture as new_task_title.
Ask: "Describe what this task should do:"
Wait for response. Capture as new_task_description.
Generate a UUID for the new task:
python3 -c "import uuid; print(uuid.uuid4())"Capture output as new_task_id.
Re-fetch the project to get the most up-to-date execution.version and the current task list for active_stage:
Call duplo-helpdesk::Projects_get with id = project_id.
Update execution_version and re-capture the existing tasks for active_stage (match by active_stage.name).
Build the full tasksToAddOrUpdate array by including all existing tasks (with their name, title, description, version) plus the new task entry at the end:
{ "name": "<new_task_id>", "title": "<new_task_title>", "description": "<new_task_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": [
{ "name": "<task.name>", "title": "<task.title>", "description": "<task.description>", "version": "<task.version>" },
...existing tasks...,
{ "name": "<new_task_id>", "title": "<new_task_title>", "description": "<new_task_description>" }
]
}
]
}Tell the user: "Task <new_task_title> added to stage <active_stage.title>."
Re-fetch the project: call duplo-helpdesk::Projects_get with id = project_id.
Find active_stage by name in the updated stages. Display:
Tasks in <active_stage.title>:
1. <task.title> — <task.description>
2. ...Ask:
"Would you like to add another task to this stage, pick a different stage, or open a ticket for one of these tasks?
- Add another task to this stage
- Pick a different stage
- Open a ticket for a task (runs /duplo:task_ticket)
- Done"
skills/task_ticket/SKILL.md with project_id, workspace_id, and active_stage already resolved (skip to its Step 2 to pick a task).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.