affaan-m/ecc

orch-add-feature

Orchestrate building a brand-new feature end to end — research, plan, TDD implementation, review, and gated commit — by delegating each phase to the matching ECC agent.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/affaan-m/ecc --skill orch-add-feature

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

orch-add-feature

Actor · action · target: orch · add · feature. Thin wrapper over the shared engine in `orch-pipeline`.

When to Use

  • The user wants a capability that does not exist yet ("add", "build",

"implement", "support …").

  • It is net-new behavior — not a correction (orch-fix-defect) and not an

alteration of existing behavior (orch-change-feature).

Operation settings

  • Default size floor: standard — run Research + Plan unless clearly small.
  • Phase mask: 0 → 1 → 2 → 4 → 5 → 6 (skip 3 Scaffold; that is MVP-only).
  • First move (phase 4): write new failing tests for the new behavior, then

implement to green.

How It Works

  1. Run the orch-pipeline engine with the settings above.
  2. Classify size first; small / trivial features collapse toward 4 → 5 → 6.
  3. Stop at Gate 1 (plan approval) and Gate 2 (pre-commit).
  4. Add security-reviewer if the feature touches a security trigger.
Related: /feature-dev is a standalone version of this flow. orch-add-feature differs by sharing the orch-pipeline engine — the size classifier and the two gates — with the rest of the family, so it right-sizes trivial features to 4 → 5 → 6.

Example

orch-add-feature: add OAuth2 login to nws-poller
→ research existing auth libs → plan task_list  [GATE 1: approve]
→ TDD each task → code-review (+ security-reviewer: auth path)
→ commit  [GATE 2: confirm]

Related by task

from this repository

More skills

All skills
affaan-m
Community

agentic-os

Build persistent multi-agent operating systems on Claude Code. Covers kernel architecture, specialist agents, slash commands, file-based memory, scheduled automation, and state management without external databases. Use when building a persistent multi-agent system on Claude Code with its own memory, commands, and scheduling.

installs
4
GitHub stars
286.1K
Updated
Oct 20
affaan-m
Community

autonomous-loops

Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems. Retained for compatibility only: when new autonomous loop guidance is needed, use continuous-agent-loop instead.

installs
4
GitHub stars
286.1K
Updated
Oct 20
affaan-m
Community

coding-standards

Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns. Use when reviewing code quality or naming with no framework-specific skill that applies.

installs
4
GitHub stars
286.1K
Updated
Oct 20
affaan-m
Community

configure-ecc

Run the conversational ECC setup wizard inside the current harness: inventory the install, collect scope (user/project/local) and hook mode (off/minimal/standard/strict) in Claude Code, use Codex's native plugin lifecycle, or install the project surface under ./.kimi-code, then preview, apply, and verify. Use when installing, updating, reconfiguring, or repairing an ECC installation, changing hook profiles, or moving ECC between install scopes.

installs
4
GitHub stars
286.1K
Updated
Oct 20