Source profileQuality 80/100

affaan-m/ECC/skills/orch-add-feature/SKILL.md

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. Use when adding a capability that does not exist yet.

Source repository stars
234,327
Declared platforms
0
Static risk flags
0
Last source update
2026-07-27
Source checked
2026-07-28

Decision brief

What it does—and where it fits

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

Best for

  • The user wants a capability that does not exist yet ("add", "build",
  • It is net-new behavior — not a correction (orch-fix-defect) and not an

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/affaan-m/ECC --skill "skills/orch-add-feature"
Safe inspection promptEditorial

Inspect the Agent Skill "orch-add-feature" from https://github.com/affaan-m/ECC/blob/4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38/skills/orch-add-feature/SKILL.md at commit 4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    When to Use

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

    The user wants a capability that does not exist yet ("add", "build",It is net-new behavior — not a correction (orch-fix-defect) and not an- 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-fea…
  2. 02

    Operation settings

    Default size floor: standard — run Research + Plan unless clearly small.

    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
  3. 03

    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.

    Run the orch-pipeline engine with the settings above.Classify size first; small / trivial features collapse toward 4 → 5 → 6.Stop at Gate 1 (plan approval) and Gate 2 (pre-commit).
  4. 04

    Example

    Review the “Example” section in the pinned source before continuing.

    Review and apply the “Example” source section.

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score80/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars234,327SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
affaan-m/ECC
Skill path
skills/orch-add-feature/SKILL.md
Commit
4e973d3eaf92d97f8d2e2d8abb39d8bdc8711b38
License
MIT
Collected
2026-07-28
Default branch
main
View the original SKILL.md

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]

Alternatives

Compare before choosing

Computed 9327

MoizIbnYousaf/marketing-cli

off-page-seo

Backlink + distribution checklist that expands a site's KD ceiling beyond what on-page work alone can earn. Use when the user mentions 'backlinks', 'off-page SEO', 'directory submissions', 'guest posts', 'outreach targets', 'link building', 'submit to directories', 'get listed in listicles', 'Product Hunt launch backlinks', or asks 'how do I get more domain authority'. Generates a prioritized, researched target list across directories, listicles, and guest-post candidates — does NOT submit anyth

Computed 9237,126

github/awesome-copilot

competitor-ad-intelligence

Use this skill when the user asks to analyze, tear down, or reverse-engineer a competitor's paid ads. Trigger for prompts like "what ads is [competitor] running", "tear down their ad strategy", "competitor ad analysis", "find ad angles we haven't tried", or "reverse-engineer their paid funnel". Do not trigger for organic/SEO competitor research or website positioning analysis.

Computed 9227

MoizIbnYousaf/marketing-cli

seo-machine

Build an organic-traffic operating system for any site or app: a multi-phase, resumable engine that ships programmatic landing pages (alternatives, comparisons, use-cases, playbooks) on top of real keyword research. Use when the user says 'SEO machine', 'build organic traffic', 'rank on Google', 'we need traffic', 'alternatives pages', 'comparison pages', '/for/ pages', 'programmatic SEO', or 'build an SEO engine'. Distinct from `seo-audit` (one-off diagnostic) and `seo-content` (single-article

Computed 9142,015

coreyhaines31/marketingskills

sales-enablement

When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. Fo