affaan-m/ecc

ecc-recipes

Map a described workflow to the right ECC command group with run-order and stop condition, or browse all command-group recipe families read live from the commands directory.

Ver código fuente

Cómo usar

  1. Copia el comando y revisa el paquete antes de instalarlo en tu entorno de agente.
  2. Consulta las herramientas, credenciales y entornos necesarios en el documento original.
  3. Describe las entradas y el resultado deseado; contrasta la salida con las fuentes.
npx skills add https://github.com/affaan-m/ecc --skill ecc-recipes

Antes de empezar

  • La instalación no incluye suscripción al modelo, cuota API ni permisos sobre tus archivos.
  • Las estrellas e instalaciones reflejan actividad, no una prueba independiente de calidad o seguridad.
Documento original del Skill

Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.

ECC Recipes

One entry point for "which group of ECC slash-commands runs my workflow, in what order, and when do I stop." Also browses every command-group recipe family.

Fills the gap between two existing skills:

  • ecc-guide — lists commands and where to read docs, but as a flat catalog.
  • prompt-optimizer — matches a task to components, but outputs a single prompt,

not a multi-command group with run-order and stop condition.

This skill adds: family grouping + run-order + stop condition.

When to Activate

  • "Which command group do I run for <workflow>?"
  • "What's the command sequence to build an MVP / fix a defect / refactor?"
  • "Show me all ECC command-group recipes" (catalog mode)
  • "How many workflow pipelines does ECC have?"
  • User invokes /ecc-recipes with or without a description.

Do Not Use When

  • User wants the task done now — route to the actual command, don't describe it.
  • User wants deep docs for ONE command — use ecc-guide.
  • User wants a draft prompt rewritten — use prompt-optimizer.

Core Principle

Answer from current files, not memory. The command set changes; never hardcode counts or member lists. Read the live commands/ directory each run, then classify into families.

Live reads

Resolve the commands directory (first that exists), then list names:

bash
for D in \
  "$HOME"/.claude/plugins/marketplaces/ecc/commands \
  "$HOME"/.claude/plugins/cache/ecc/ecc/*/commands \
  ./commands \
  ./.claude/commands \
  "$HOME"/.claude/commands; do
  [ -d "$D" ] && CMD_DIR="$D" && break
done
[ -z "${CMD_DIR:-}" ] && { echo "No ECC commands directory found."; return 1; }
find "$CMD_DIR" -maxdepth 1 -name '*.md' -exec basename {} .md \; | sort

Optionally read manifests/install-*.json if present for richer grouping. Use the smallest set of reads needed.

Family Classification (by prefix)

Group command names by leading prefix; map known singletons by hand. Families are derived live — the table below is the classification rule, not a frozen list.

Family prefixRecipe meaningTypical run-order
orch-*gated Research, Plan, TDD, Review, Commit per task typepick one orch-* by task kind; it runs its own internal phases
multi-*multi-model workflowmulti-plan then multi-execute then review (or multi-workflow end-to-end)
prp-*PRD to plan to implement to PR pipelineprp-prd then prp-plan then prp-implement then prp-commit then prp-pr
epic-*large multi-unit epic, parallelepic-decompose then epic-claim then epic-validate then epic-review then epic-unblock then epic-sync then epic-publish
loop-*managed autonomous loop and monitorloop-start <pattern> then watch with loop-status
gan-*generator and evaluator loopgan-build (code) or gan-design (UI); self-looping
*-build / *-review / *-testper-language CI triad<lang>-test (TDD) then <lang>-build (fix) then <lang>-review
hookify-*behavior-hook managementhookify then hookify-list then hookify-configure
learn / instinct-* / evolve / promote / prunecontinuous-learninglearn then instinct-status then evolve then promote
singletonssanta-loop, plan, plan-prd, pr, code-review, checkpoint, etc.standalone or glue between groups

Any command not matching a prefix rule → list it under singletons with its one-line description.

How It Works

1. Live-read command names from CMD_DIR.
2. Classify into families by prefix and a singleton map.
3. If a workflow description was given -> MATCH MODE.
   If none -> CATALOG MODE.
4. Advisory only: print the plan. Never run the matched commands.

Catalog mode (no description)

Output the family table: each family, member count, members, one-line meaning, typical run-order. End with the total command count and a prompt to describe a workflow for a matched recipe.

Match mode (description given)

  1. Restate the workflow in one sentence.
  2. Pick the best 1-2 families; say WHY in one line each.
  3. Run-order block — exact command sequence for the matched family.
  4. Stop condition — always explicit (max-runs, completion-signal,

review-passes, or single-shot). For autonomous loops, warn about subscription burn and recommend a backstop bound.

  1. Where to read — the commands/<name>.md path plus /ecc-guide <name>.

Output Template (match mode)

Workflow: <one-sentence restatement>

Best fit: <family> — <why>
(Alt: <family> — <why>)

Run-order:
  /<cmd1>   # job
  /<cmd2>   # job
  /<cmd3>   # job
  STOP when: <condition>
  WARNING (autonomous loops only): an unbounded loop burns subscription/credits —
  add a max-iteration or max-cost backstop alongside the completion signal.

Read full docs:
  commands/<cmd1>.md   (or: /ecc-guide <cmd1>)

Examples

Catalog: /ecc-recipes → prints the family table and total count.

Match: /ecc-recipes plan a whole app upfront then auto-build with adversarial review until done → Best fit: loop-* (autonomous) wrapping gan-* or santa-loop (adversarial). Run-order: plan-prd then loop-start rfc-dag --mode safe then monitor loop-status; STOP when all units pass review N consecutive times (add a max-iteration backstop to bound burn).

Match: /ecc-recipes fix a bug in my Go service → Best fit: orch-fix-defect (reproduce, fix, review, commit). Alt: go-test then go-build then go-review. STOP: regression test green and review pass.

Non-Goals

  • Not an executor — advisory only.
  • Not per-command deep docs — that's ecc-guide.
  • Not prompt rewriting — that's prompt-optimizer.
  • Never hardcode command counts or member lists — always live-read.

Relacionados por tarea

del mismo repositorio

Más Skills

Todos los Skills
affaan-m
Comunidad

rust-testing

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology. Use when writing Rust tests — unit, integration, async, property-based, or coverage.

Instalaciones / 24h
489
GitHub Stars
308,2 mil
Actualizado
20 nov
affaan-m
Comunidad

search-first

Research-before-coding workflow: search npm/PyPI, MCP servers, skills, and GitHub for existing tools before writing custom code, then adopt, extend, or build. Launches the researcher agent for non-trivial needs. Use when starting a feature, adding a dependency or integration, or about to write a utility that may already exist.

Instalaciones / 1h
5
GitHub Stars
308,2 mil
Actualizado
20 nov
affaan-m
Comunidad

browser-qa

Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction tests, screenshot visual regression across three breakpoints, and axe-core accessibility audits ending in a SHIP / DO-NOT-SHIP verdict. Use when testing a deployed feature on staging or preview, before shipping frontend changes, reviewing a frontend PR, or checking responsive layout and accessibility.

Instalaciones / 1h
2
GitHub Stars
307,9 mil
Actualizado
20 nov
affaan-m
Comunidad

docker-patterns

Docker and Docker Compose patterns for local development, hardened CLI installer harnesses, container security, networking, volumes, and multi-service orchestration. Use when creating or reviewing Dockerfiles and Compose services, testing installers across Linux distributions, or planning accurate native macOS and Windows validation.

Instalaciones / 1h
2
GitHub Stars
307,9 mil
Actualizado
20 nov