affaan-m/ecc

orch-pipeline

Shared orchestration engine behind the orch- skill family — the gated Research-Plan-TDD-Review-Commit pipeline, size classifier, agent and command map, and two human gates (plan approval, commit confirmation) that orch- operation skills delegate to.

Quelltext ansehen

Verwendung

  1. Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
  2. Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
  3. Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/affaan-m/ecc --skill orch-pipeline

Vor dem Start

  • Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
  • Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

Orchestrator Pipeline (shared engine)

The orch-* skills are thin wrappers. They do not re-implement any work — they classify the request, choose which phases of this pipeline run, and delegate each phase to an existing ECC agent or command. This file is that pipeline.

Invoke an operation skill (orch-add-feature, orch-fix-defect, …) rather than this engine directly. This file is the reference they point at.

When to Use

  • Loaded indirectly whenever an orch-* operation skill runs.
  • Read directly only when adding a new operation to the family or tuning the

shared phases, gates, or agent map.

The operation family

SkillOperationTriggerFirst move
orch-add-featurefeaturecapability does not exist yetresearch + plan a new slice
orch-change-featuretweakworks, but desired behavior differsamend existing behavior and its tests
orch-fix-defectfixbroken; behavior is wrongreproduce as a failing test, then fix
orch-refine-coderefactorbehavior stays, structure improvesrestructure while keeping tests green
orch-build-mvpmvpbootstrap from a design/spec docingest doc → vertical slices
These wrappers compose existing ECC commands rather than replace them: /feature-dev, /plan, /code-review, /build-fix, /refactor-clean, and /gan-build, plus the tdd-workflow skill. The orch-* family adds the shared size classifier and the two gates on top of them, so one umbrella covers all five operations consistently.

Step 0 — Classify size (right-sizing)

Ceremony scales to blast radius. Score the request on three signals, take the highest tier any signal reaches, and state the result in one line so the user can override:

TierFiles touchedNew dependency / contractDesign ambiguityPhases that run
trivial1, a few linesnonenone — the change is obvious4 → 5 → 6
small1 file / 1 functionnoneclear once you read the code(1 light) → 4 → 5 → 6
standard2–5 filesmaybe a new internal moduleone real choice to make1 → 2 → 4 → 5 → 6
largemany / cross-cuttingnew external dep, public API, or a spec docmultiple open questions1 → 2 → (3) → 4 → 5 → 6

Phase 0 (Intake) always runs and is omitted from the mask column above. The tie-breaker: anything touching a security trigger (below) or a public API / contract is at least standard, regardless of file count.

The phases

Each phase delegates — it does not do the work inline.

  • 0. Intake — restate the request. For orch-build-mvp, read the spec/design

doc and extract scope, locked decisions, and a feature list.

  • 1. Research & Reuse — per rules/common/development-workflow.md: gh search repos /

gh search code, then Context7 / vendor docs, then package registries, then Exa. Prefer adopting a proven implementation over net-new code.

  • 2. Plan — delegate to the planner agent (or architect /

code-architect for structural decisions). Output a task_list ordered as thin vertical slices. → GATE 1.

  • 3. Scaffold — orch-build-mvp only: stand up the first end-to-end slice.
  • 4. Implement (TDD) — drive each task through the tdd-guide agent (or the tdd-workflow skill):

red → green → refactor. Honor the operation's first-move rule.

  • 5. Review — code-reviewer agent / /code-review. Add security-reviewer

whenever the diff touches a security trigger (below).

  • 6. Commit — conventional commits (feat: / fix: / refactor: / …), one

per logical chunk. → GATE 2.

The two gates

This family is gated, not autonomous:

  1. GATE 1 — after Plan. Present the task_list; do not write implementation

code until the user approves.

  1. GATE 2 — before Commit. Present the diff summary and proposed messages;

do not commit until the user confirms.

Everything between the gates flows without stopping.

Agent / command map

PhasePrimaryFallback / escalation
Intake / understandcode-explorertrace existing paths before a tweak, fix, or refactor
Planplannerarchitect, code-architect for structural calls
Implementtdd-guide (or tdd-workflow skill)build-error-resolver / /build-fix on build breaks
Reviewcode-reviewer / /code-reviewlanguage reviewer (python-reviewer, typescript-reviewer, …)
Securitysecurity-reviewer—
MVP inner loop/gan-build "<brief>" --skip-plannerdrives gan-generator → gan-evaluator; tune --max-iterations / --pass-threshold

Match the language reviewer to the repo (see the repo's own CLAUDE.md).

Security-review trigger

Pull in security-reviewer when the diff touches any of: authentication or authorization, user-input handling, database queries, file-system paths, external API calls, cryptography, or secrets / credentials. (Per rules/common/security.md.)

Handoff artifacts

The pipeline carries no hidden state — the planning docs are the handoff:

  • task_list (from Plan) drives the Implement loop.
  • Larger work may also emit PRD / architecture / system_design under the repo's

docs/ per rules/common/development-workflow.md.

  • Review findings (CRITICAL / HIGH) must be resolved before Gate 2.

Verification

  • size tier was stated and matched the work
  • Gate 1 (plan) and Gate 2 (commit) were both honored
  • security-reviewer ran iff a security trigger was touched
  • commits are conventional and scoped to one logical change
  • new / changed behavior has tests; coverage ≥ 80% per rules/common/testing.md

Verwandte Aufgaben

aus demselben Repository

Weitere Skills

Alle Skills
affaan-m
Community

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.

Installationen / 24h
489
GitHub Stars
308.228
Aktualisiert
20. Nov.
affaan-m
Community

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.

Installationen / 1h
5
GitHub Stars
308.228
Aktualisiert
20. Nov.
affaan-m
Community

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.

Installationen / 1h
2
GitHub Stars
307.864
Aktualisiert
20. Nov.
affaan-m
Community

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.

Installationen / 1h
2
GitHub Stars
307.864
Aktualisiert
20. Nov.