mirror of
https://github.com/affaan-m/ECC.git
synced 2026-11-13 19:42:10 +00:00
Affaan Mustafa
c05b2d6614
* 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.
38 lines
878 B
Markdown
38 lines
878 B
Markdown
---
|
|
name: feature-development
|
|
description: Workflow command scaffold for feature-development in ECC.
|
|
allowed-tools: ["Bash", "Read", "Write", "Grep", "Glob"]
|
|
---
|
|
|
|
# /feature-development
|
|
|
|
Use this workflow when working on **feature-development** in ECC.
|
|
|
|
## Goal
|
|
|
|
Standard feature implementation workflow
|
|
|
|
## Common Files
|
|
|
|
- `manifests/*`
|
|
- `schemas/*`
|
|
- `**/*.test.*`
|
|
- `**/api/**`
|
|
|
|
## Suggested Sequence
|
|
|
|
1. Understand the current state and failure mode before editing.
|
|
2. Make the smallest coherent change that satisfies the workflow goal.
|
|
3. Run the most relevant verification for touched files.
|
|
4. Summarize what changed and what still needs review.
|
|
|
|
## Typical Commit Signals
|
|
|
|
- Add feature implementation
|
|
- Add tests for feature
|
|
- Update documentation
|
|
|
|
## Notes
|
|
|
|
- Treat this as a scaffold, not a hard-coded script.
|
|
- Update the command if the workflow evolves materially. |