/plan-canvas
Open a plan or HTML artifact in the browser Plan Canvas for annotate-and-approve review. This is a thin slash-command entrypoint over the plan-canvas skill, which covers the full workflow and rules.
> /plugin marketplace add affaan-m/ECC> /plugin install ecc@ecc
Command definition
plan-canvas.mddescription: Open a plan or HTML artifact in the browser Plan Canvas for annotate-and-approve review. This is a thin slash-command entrypoint over the plan-canvas skill, which covers the full workflow and rules.
argument-hint: "[path/to/artifact.plan.md | path/to/artifact.html]"
Plan Canvas Command
Opens a local artifact in the Plan Canvas — ECC's browser review surface — where the user annotates elements, chats with you, and approves the plan or requests changes without leaving the page.
This command is a thin entry point over the `plan-canvas` skill. Follow that skill for the full workflow and rules.
What This Command Does
1. Resolve the artifact: the given path, else the most recently modified `.claude/plans/*.plan.md`, else ask what to review. 2. `ecc-plan-canvas open <artifact>` — opens the user's browser. 3. `ecc-plan-canvas await <artifact>` — block until feedback, verdict, or session end; leave it running. 4. Apply feedback to the artifact file (the canvas live-reloads), answer with `await <artifact> --reply "..."`, and repeat until the user approves or ends the session.
An `approve` verdict counts as plan confirmation for `/plan`-style gates: stop polling, `end` the session, and begin implementation.
Example
User: /plan-canvas .claude/plans/notifications.plan.md
Assistant: (runs open + await, browser opens)
...user clicks "Request changes" with two annotations...
Assistant: (edits the plan, replies in-canvas, awaits again)
...user clicks "Approve plan"...
Assistant: Plan approved in the canvas — starting implementation.
Related
- `plan-canvas` skill — full workflow, feedback JSON shapes, rules
- `/plan` — produces the plan artifacts this reviews
- Source: `scripts/plan-canvas.js`, `scripts/lib/plan-canvas/`
Read more
description: Open a plan or HTML artifact in the browser Plan Canvas for annotate-and-approve review. This is a thin slash-command entrypoint over the plan-canvas skill, which covers the full workflow and rules. argument-hint: "[path/to/artifact.plan.md | path/to/artifact.html]"
Plan Canvas Command
Opens a local artifact in the Plan Canvas — ECC's browser review surface — where the user annotates elements, chats with you, and approves the plan or requests changes without leaving the page.
This command is a thin entry point over the `plan-canvas` skill. Follow that skill for the full workflow and rules.
What This Command Does
1. Resolve the artifact: the given path, else the most recently modified `.claude/plans/*.plan.md`, else ask what to review. 2. `ecc-plan-canvas open <artifact>` — opens the user's browser. 3. `ecc-plan-canvas await <artifact>` — block until feedback, verdict, or session end; leave it running. 4. Apply feedback to the artifact file (the canvas live-reloads), answer with `await <artifact> --reply "..."`, and repeat until the user approves or ends the session.
An `approve` verdict counts as plan confirmation for `/plan`-style gates: stop polling, `end` the session, and begin implementation.
Example
User: /plan-canvas .claude/plans/notifications.plan.md Assistant: (runs open + await, browser opens) ...user clicks "Request changes" with two annotations... Assistant: (edits the plan, replies in-canvas, awaits again) ...user clicks "Approve plan"... Assistant: Plan approved in the canvas — starting implementation.
Related
- `plan-canvas` skill — full workflow, feedback JSON shapes, rules
- `/plan` — produces the plan artifacts this reviews
- Source: `scripts/plan-canvas.js`, `scripts/lib/plan-canvas/`
Your agent can write code, but ECC gives it a coordinated engineering system and toolbox: it plans before it builds, verifies changes with tests, reviews its own work from a fresh context, remembers what matters, and turns repeated wins into reusable skills
Other commands on ecc.
More commands from other plugins.
build
CommandImplement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.

