Files
ECC/.claude/research/ecc-research-playbook.md
T
Affaan Mustafa c05b2d6614 chore: retire the Everything Claude Code name, ECC only (#3330)
* chore: retire the Everything Claude Code name, ECC only

Replace the expanded product name and the everything-claude-code slug
with ECC across READMEs, translated docs, harness folders, skills,
commands, scripts and examples. Repo URLs now point at affaan-m/ECC.

Rename repo-internal artifacts to ecc forms (ecc-conventions skill,
ecc-guardrails, ecc-research-playbook, ecc-team-config, ecc-instincts
with ecc-* ids) and update .claude/ecc-tools.json.

Legacy install ids, plugin dirs, package names and MCP prefixes stay
where existing installs resolve against them. The codex global-state
check and harness-audit repo detection accept the new name first and
the legacy one as a fallback. The Discord bot prefers ~/GitHub/ECC and
falls back to the nested legacy checkout path.

Refresh the skill-triggers registryDigest for the changed skill text.

* fix(ecc-tools): drop managed paths to the removed Claude repo skill

.claude/skills/<repo-skill>/SKILL.md was deleted in #2770 but stayed listed in
ecc-tools.json and the team config. Remove those entries and point the Claude
Code adapter at the existing .agents/skills/ecc-conventions/SKILL.md.
2026-10-01 17:50:41 -05:00

588 B

ECC Research Playbook

Use this when the task is documentation-heavy, source-sensitive, or requires broad repository context.

Defaults

  • Prefer primary documentation and direct source links.
  • Include concrete dates when facts may change over time.
  • Keep a short evidence trail for each recommendation or conclusion.

Suggested Flow

  1. Inspect local code and docs first.
  2. Browse only for unstable or external facts.
  3. Summarize findings with file paths, commands, or links.

Repo Signals

  • Primary language: JavaScript
  • Framework: Not detected
  • Workflows detected: 10