Clear spec, plan, and/or execution tasks for the active project based on the user's natural language request. Clearing cascades downstream — clearing spec also clears plan and execution; clearing plan also clears execution. Loops back into the AI Planner at the correct phase after clearing. Requires an active project.
IMPORTANT: Only execute this skill when the user explicitly asks to clear or reset the spec, plan, or canvas files. Never invoke it automatically. This skill is project-scoped — a project_id must be present in state.
Follow these steps in order:
Read .duplocloud/state.toon.
project_id is absent or file missing: stop and tell the user:
"No active project found. Please run
/duplo:activate_projectfirst."
Capture project_id and project_name.
Interpret the user's message and apply the cascade rule: clearing any artifact also clears everything downstream in the spec → plan → execution chain.
| User mentions | clear_set |
|---|---|
| spec (any mention) | spec + plan + execution |
| plan (without spec) | plan + execution |
| execution / tasks (without spec or plan) | execution only |
| "all", "everything", "canvas", "reset" | spec + plan + execution |
Examples:
{spec, plan, execution}{spec, plan, execution} (spec cascades anyway){plan, execution}{execution}{spec, plan, execution}Do not ask the user to pick from a list — the cascade rule fully resolves clear_set from their words.
Build a bullet list from clear_set and show:
"This will permanently clear the following for project <project_name> on the platform:
- <Spec — if in clear_set>
- <Plan — if in clear_set>
- <Execution tasks — if in clear_set>
This cannot be undone. Continue? (y/n)"
3a — If clear_set contains spec or plan:
Call duplo-helpdesk::Projects_patch with id = project_id and body (include only what is in clear_set):
{
"spec": { "content": "" },
"plan": ""
}3b — If clear_set contains execution:
Call duplo-helpdesk::Projects_update_plan_execution with id = project_id and body:
{
"canvas_files": []
}Tell the user what was cleared:
"Cleared: <comma-separated list> for <project_name>."
Re-entry phase — earliest in chain that was cleared:
| clear_set contains | Re-entry phase |
|---|---|
spec | spec |
plan (no spec) | plan |
execution only | execution |
Tell the user:
"Starting AI Planner from the <re-entry phase> phase now."
Then read and follow skills/ai_planner/SKILL.md from Step 2 onwards (project is already verified — skip Step 0).
In AI Planner Step 2 (phase detection), skip re-detection — instead use the re-entry phase from above and jump directly to:
| Re-entry phase | AI Planner step |
|---|---|
| spec | Step 3 (spec phase) |
| plan | Step 4 (plan phase) |
| execution | Step 5 (execution phase) |
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.