executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
agent-workflowCreate, update, run, resume, or continue agent workflows. Use when the user asks to create or fix workflow JSON, execute an existing workflow, run a workflow with a prompt, resume a workflow run, or continue the next node in a waiting multi-step workflow.
Independent GitHub snapshot · Automated classification · Original documentation governs
Create, update, run, and continue agent workflows while keeping workflow files valid and terminal execution human-in-the-loop aware.
Workflow JSON keeps runnable nodes as type: "agent". Agent node data uses data.subagent for a Skill Pilot subagent from core/subagents/*/*.md; do not use data.skill for workflow nodes.
As an expert in your assigned roles, you must announce your actions before performing them using the following format:
As a {Role, and Role-XYZ if have more roles}, I will {action description}
This communication pattern ensures transparency and allows for human-in-the-loop oversight at key decision points.
Follow these steps in order:
references/create-update-workflow.md.references/execute-workflow-action.md.references/continue-workflow-action.md.Open the one reference file that matches the selected case. Load additional references only when that case explicitly requires them.
Follow the selected reference file exactly. Keep generated workflow files under core/workflows/ by default, and keep any temporary or intermediate helper files under .skillpilot/temp/ unless the user explicitly requested another project-local path.
Run the validation or execution checks required by the selected case. Report the resulting file path, command, output summary, or blocker in concise language.