Communitygithub.com

orch-change-feature

기존에 작동 중인 기능을 새로운 원하는 동작으로 변경하는 과정을 조율합니다. 테스트를 새로운 사양에 맞게 업데이트하고, 구현을 변경한 후, 검토 및 게이트된 커밋을 수행합니다. 동작이 고장나지 않았지만 달라져야 할 때 사용합니다.

orch-change-feature란 무엇인가요?

이 스킬은 이미 작동 중인 기능의 동작을 변경해야 할 때 사용하는 오케스트레이션 스킬입니다. 기능이 고장난 것이 아니라 단순히 동작 방식을 조정하거나 수정해야 하는 경우에 적합하며, 버그 수정(`orch-fix-defect`)이나 새로운 기능 추가(`orch-add-feature`)와는 구분됩니다. 주로 `orch-pipeline` 엔진을 기반으로 동작하며, 변경 프로세스는 새로운 동작을 반영하도록 기존 테스트를 먼저 업데이트(4단계)한 후, 테스트를 통과하도록 구현을 변경하는 방식으로 진행됩니다. 기본 작업 크기는 'small'로 설정되어 있으며, 보안 트리거가 있는 변경에는 보안 검토자가 자동으로 추가됩니다.

지원 대상✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/affaan-m/ECC/tree/main/skills/orch-change-feature

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

문서

orch-change-feature은(는) 무엇을 하나요?

Actor · action · target: orch · change · feature. 공유 엔진인 orch-pipeline을 감싸는 얇은 래퍼입니다.

사용 시기

  • 기존 기능이 작동하지만, 원하는 동작이 다른 경우 ("변경", "조정", "또한 … 하게 만들기", "X 대신 Y 수행").
  • 다음 관련 스킬과 구분하십시오:
    • 고장난 경우 → orch-fix-defect 아님 (재현할 버그 없음).
    • 새로운 경우 → orch-add-feature 아님 (기능이 이미 존재함).

작업 설정

  • 기본 크기 하한: small — 대부분의 조정은 함수 하나 또는 둘 수준입니다.
  • 단계 마스크: 0 → (새 동작에 연구가 필요한 경우에만 1) → 간단한 2 → 4 → 5 → 6.
  • 첫 번째 단계 (4단계): 새로운 원하는 동작을 표현하도록 기존 테스트를 업데이트한 후, 테스트를 통과할 때까지 구현을 변경합니다. 테스트를 먼저 변경하는 것이 조정과 수정을 구분짓는 요소입니다.

작동 방식

  1. 위 설정으로 orch-pipeline 엔진을 실행합니다.
  2. 계획은 가볍게 유지합니다 — standard+ 크기인 경우에만 전체 planner 단계가 필요합니다.
  3. 게이트 1 (계획 / 변경된 테스트 승인)과 게이트 2 (커밋 전)에서 멈춥니다.
  4. 변경 사항이 보안 트리거에 영향을 미치는 경우 security-reviewer를 추가합니다.

예시

orch-change-feature: nws-poller가 3개 대신 2개의 경고에서 알림을 보내도록 변경
→ 임계값 테스트를 새 사양으로 업데이트 → 구현을 변경하여 테스트 통과
→ 코드 리뷰 → 커밋  [게이트 2: 확인]

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

accessibility

Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA. Use when building or auditing UI that must meet WCAG 2.2 Level AA, or when reviewing a change for keyboard, contrast, or screen-reader support.

affaan-m/content-engine

Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.

affaan-m/ECC

Multi-platform content distribution across X, LinkedIn, Threads, and Bluesky. Adapts content per platform using content-engine patterns. Never posts identical content cross-platform. Use when the user wants to distribute content across social platforms.

affaan-m/fal-ai-media

Unified media generation via fal.ai MCP — image, video, and audio. Covers text-to-image (Nano Banana), text/image-to-video (Seedance, Kling, Veo 3), text-to-speech (CSM-1B), and video-to-audio (ThinkSound). Use when the user wants to generate images, videos, or audio with AI.

affaan-m/manim-video

日本語翻訳:このファイルは manim-video 用の日本語翻訳が必要です

affaan-m/remotion-video-creation

Remotion のベストプラクティス - React で動画を作成する。3D、アニメーション、音声、字幕、チャート、トランジションなどをカバーするドメイン固有の29のルール。

affaan-m/video-editing

AI-assisted video editing workflows for cutting, structuring, and augmenting real footage. Covers the full pipeline from raw capture through FFmpeg, Remotion, ElevenLabs, fal.ai, and final polish in Descript or CapCut. Use when the user wants to edit video, cut footage, create vlogs, or build video content.

agent-architecture-audit

Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution, tool discipline failures, hidden repair loops, and rendering corruption. Produces severity-ranked findings with code-first fixes. Essential for developers building agent applications, autonomous loops, or any LLM-powered feature. Use when an agent or LLM feature misbehaves and the failing layer is unknown, or before shipping an agent stack.

agent-eval

Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics. Use when choosing between coding agents, or when a change to an agent setup needs measured pass rate, cost, and time rather than an impression.

agent-harness-construction

Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates. Use when defining or revising an agent

agentic-engineering

Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing. Use when planning or executing engineering work that agents will carry out end to end.

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.

agent-introspection-debugging

Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.

agent-payment-x402

Add x402 payment execution to AI agents with per-task budgets, spending controls, and non-custodial wallets. Supports Base through agentwallet-sdk and X Layer through OKX Payments / OKX Agent Payments Protocol. Use when an agent must pay for something itself and needs per-task budgets, spending controls, and a non-custodial wallet.

agent-self-evaluation

Use after completing any non-trivial task. The agent self-rates its output on 5 axes — accuracy, completeness, clarity, actionability, conciseness — with concrete evidence per criterion. Produces a structured 1-5 scorecard with specific improvement suggestions.

agent-sort

Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

ai-first-engineering

Engineering operating model for teams where AI agents generate a large share of implementation output. Use when setting team process, review gates, or ownership rules for a codebase largely written by agents.

ai-regression-testing

Regression testing strategies for AI-assisted development. Sandbox-mode API testing without database dependencies, automated bug-check workflows, and patterns to catch AI blind spots where the same model writes and reviews code. Use when adding regression coverage to AI-assisted code, or when the same model both wrote and reviewed a change.

android-clean-architecture

Clean Architecture patterns for Android and Kotlin Multiplatform projects — module structure, dependency rules, UseCases, Repositories, and data layer patterns. Use when structuring modules, layers, or data flow in an Android or KMP project.

angular-developer

Generates Angular code and provides architectural guidance. Trigger when creating projects, components, or services, or for best practices on reactivity (signals, linkedSignal, resource), forms, dependency injection, routing, SSR, accessibility (ARIA), animations, styling (component styles, Tailwind CSS), testing, or CLI tooling.

관련 스킬