Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@skills/plan-orchestrate/SKILL.md` around lines 24 - 25, The manifest allows
"--lang=flutter" and references "flutter-reviewer", but that reviewer agent
isn't available and will create invalid /orchestrate chains; either remove
"--lang=flutter" from the allowed language flag list and any references to
"flutter-reviewer" (e.g., the language mapping and reviewer lists), or replace
them with the correct shipped reviewer name for Flutter; update every occurrence
of "--lang=flutter" and "flutter-reviewer" in SKILL.md (including the language
flag example, the reviewer mapping, and any orchestration examples) so the CLI
flag and /orchestrate chains only reference supported reviewer agents.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@skills/plan-orchestrate/SKILL.md` around lines 53 - 54, Replace the hardcoded
"everything-claude-code" namespace used for plugin commands in SKILL.md with the
actual ECC namespace "ecc" so plugin-mode commands resolve correctly: update
occurrences of "/everything-claude-code:orchestrate" to "/ecc:orchestrate" and
"everything-claude-code:<name>" to "ecc:<name>" (also fix the same instances
noted around lines 163-164 and 244-245), ensuring both the slash-prefixed
command forms and the agent prefix forms use "ecc".

Check if this issue is valid — if so, understand the root cause and fix it. At skills/plan-orchestrate/SKILL.md, line 53:

<comment>Plugin-mode command and agent namespace are hardcoded to `everything-claude-code`, which conflicts with the repo’s canonical `ecc@ecc` / `/ecc:*` namespace and can generate non-working orchestrate commands.</comment>

<file context>
@@ -0,0 +1,262 @@
+
+| Form | Detection | `{ORCH_CMD}` | Agent name format |
+|---|---|---|---|
+| Plugin install (1.9.0+) | `<claude-home>/plugins/marketplaces/everything-claude-code/` exists | `/everything-claude-code:orchestrate` | `everything-claude-code:<name>` |
+| Legacy bare install | Above absent; agent files under `<claude-home>/agents/` | `/orchestrate` | `<name>` |
+
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At skills/plan-orchestrate/SKILL.md, line 142:

<comment>Build-chain resolution produces an invalid agent for Flutter (`flutter-build-resolver`). Add an explicit Flutter mapping (e.g., to `dart-build-resolver`) or fallback to `build-error-resolver`.</comment>

<file context>
@@ -0,0 +1,262 @@
+3. `impl` + `db` → `tdd-guide,database-reviewer,<lang>-reviewer`.
+4. **Deduplicate** the resulting chain (preserve first occurrence). E.g. `review` + `lang=unknown` would yield `code-reviewer,code-reviewer` after rule 5; deduplication collapses it to `code-reviewer`.
+5. `<lang>-reviewer` resolves to `code-reviewer` when `lang=unknown`.
+6. `<lang>-build-resolver` resolves to `build-error-resolver` when `lang=unknown`. **Special case**: if Phase 0 set `pytorch=true`, use `pytorch-build-resolver` for `build` chains regardless of `<lang>`. There is no `python-build-resolver`; `--lang=python` without `pytorch=true` resolves to `build-error-resolver`.
+7. **Zero-tag steps**: if no trigger word matches, set chain to `code-reviewer` and write `no tag matched; default review-only chain` under "Chain rationale".
+8. Chain length ≤ 4 after deduplication. If exceeded, drop weakest tag (`lookup` and `docs` first).
</file context>