mirror of
https://github.com/affaan-m/ECC.git
synced 2026-08-21 15:02:23 +02:00
* feat: add Plan Canvas - browser annotate-and-approve review for plan artifacts - scripts/plan-canvas.js CLI (open/await/end/stop/server; bin ecc-plan-canvas) - loopback server + ECC-styled chrome + annotation SDK + zero-dep markdown renderer - Approve/Request-changes verdicts wired to the /plan confirmation gate - plan-canvas skill, /plan-canvas command, SessionStart hook surfacing open reviews - shared scripts/lib/loopback-guard.js extracted from control-pane (API re-exported) - 121 new tests incl. full-workflow E2E; registered in manifests, catalog, registry Inspired by lavish-axi (https://github.com/kunchenguid/lavish-axi) by @kunchenguid; original ECC-native implementation, not a port. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * refactor(plan-canvas): invoke via ecc-plan-canvas bin so the skill works from any project Skill/command referenced a cwd-relative `node scripts/plan-canvas.js`, unusable outside the ECC root. Switch to the ecc-plan-canvas bin (and $CLAUDE_PLUGIN_ROOT fallback) and align CLI next_step hints so an agent can run it as a skill in any repo. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * feat(plan-canvas): render Mermaid diagrams + ship Codex cross-harness surface - markdown renderer emits <pre class="mermaid"> for ```mermaid blocks (source entity-escaped so the browser decodes it for the renderer while blocking injection) - artifact template loads a pinned Mermaid build only when a diagram is present, themed to ECC dark, securityLevel strict, graceful offline fallback to source (ECC_PLAN_CANVAS_MERMAID_URL overrides for a local mirror) - skill teaches Mermaid-for-diagrams and states the CLI+JSON loop is harness-agnostic - add .agents/skills/plan-canvas (Codex) with agents/openai.yaml interface manifest - register in install-modules workflow-quality paths; docs updated Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * docs(plan-canvas): add demo screenshot Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix(ci): sync yarn.lock with new bin; add contributor checklist - yarn.lock records the ecc-plan-canvas bin so Yarn hardened-mode install no longer wants to modify the lockfile on public PRs - PR template + CONTRIBUTING gain a pre-push checklist covering the lockfile trap and the full skill/command/CLI registration surfaces Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Haley Chen <2022hachen@gmail.com> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
46 lines
1.7 KiB
Markdown
46 lines
1.7 KiB
Markdown
---
|
|
description: Open a plan or HTML artifact in the browser Plan Canvas for annotate-and-approve review
|
|
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/`
|