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
planPlan mode — inspect context, write a markdown plan into the active workspace's `.echo-agent/plans/` directory, and do not execute the work.
Independent GitHub snapshot · Automated classification · Original documentation governs
.echo-agent/plans/ directory, and do not execute the work.
version: 1.0.0
metadata:
echo:
tags: [planning, plan-mode, implementation, workflow]Use this skill when the user wants a plan instead of execution.
For this turn, you are planning only.
.echo-agent/plans/.Write a markdown plan that is concrete and actionable.
Include, when relevant:
If the task is code-related, include exact file paths, likely test targets, and verification steps.
Save the plan with write_file under:
.echo-agent/plans/YYYY-MM-DD_HHMMSS-<slug>.mdUse this path relative to the active working directory.
If the runtime provides a specific target path, use that exact path.
If not, create a sensible timestamped filename yourself under .echo-agent/plans/.
/plan, infer the task from the current conversation context.