사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/affaan-m/ecc --skill agentic-engineering시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Agentic Engineering
Use this skill for engineering workflows where AI agents perform most implementation work and humans enforce quality and risk controls.
Operating Principles
- Define completion criteria before execution.
- Decompose work into agent-sized units.
- Route model tiers by task complexity.
- Measure with evals and regression checks.
Eval-First Loop
- Define capability eval and regression eval.
- Run baseline and capture failure signatures.
- Execute implementation.
- Re-run evals and compare deltas.
Task Decomposition
Apply the 15-minute unit rule:
- each unit should be independently verifiable
- each unit should have a single dominant risk
- each unit should expose a clear done condition
Model Routing
- Haiku: classification, boilerplate transforms, narrow edits
- Sonnet: implementation and refactors
- Opus: architecture, root-cause analysis, multi-file invariants
Session Strategy
- Continue session for closely-coupled units.
- Start fresh session after major phase transitions.
- Compact after milestone completion, not during active debugging.
Review Focus for AI-Generated Code
Prioritize:
- invariants and edge cases
- error boundaries
- security and auth assumptions
- hidden coupling and rollout risk
Do not waste review cycles on style-only disagreements when automated format/lint already enforce style.
Interpret Tool Results Before Comparing Data
For document reads and processing loops, check three boundaries in order:
- Check the tool/transport envelope for an error or an indeterminate outcome.
- Decode the response and check operation status using that tool's documented
contract. An outer success flag or a present payload does not establish that the requested operation succeeded. Status may live in structured content, decoded text, or another documented field; result.ok is not a universal MCP field. Missing or unrecognized status stays unknown.
- Only after confirmed operation success, validate the document shape and compare
its fields. An operation failure is not a document identity mismatch.
Keep the operation name, request/correlation ID when available, relevant status and error details, and the original response needed for diagnosis. Redact secrets and private document data before logging or sharing. Do not reconstruct missing responses from a later response's shape.
Portable Classification Example
The adapter below uses an illustrative read-tool contract, not an MCP schema: isError is a required boolean; when false, result.ok is a required operation status. A successful read returns result.document with a string id; a failed read may carry result.error. Replace this adapter with the actual tool's contract, including its documented decoding and document validation rules.
function decodeRead(response) {
if (!response || typeof response.isError !== 'boolean') {
return { kind: 'unknown_response' };
}
if (response.isError) return { kind: 'tool_error' };
const result = response.result;
if (result?.ok === false) {
return { kind: 'operation_error', error: result.error };
}
if (result?.ok !== true) return { kind: 'unknown_response' };
const document = result.document;
if (!document || typeof document.id !== 'string') {
return { kind: 'invalid_document' };
}
return { kind: 'document', document };
}
function inspectRead(response, expectedId, decode = decodeRead) {
const outcome = decode(response);
if (outcome.kind !== 'document') return outcome;
return outcome.document.id === expectedId
? { kind: 'match', document: outcome.document }
: { kind: 'field_mismatch', actualId: outcome.document.id, expectedId };
}Synthetic evaluation cases (not a reproduction of any historical incident):
| Input under this illustrative contract | Expected classification |
|---|---|
isError: true | tool_error; no field comparison |
isError: false, result.ok: false, maintenance error, no document | operation_error; preserve maintenance details, no mismatch |
isError: false, missing operation status | unknown_response; no field comparison |
| Confirmed success, missing document or non-string ID | invalid_document; no field comparison |
| Confirmed success, valid document with expected ID | match |
| Confirmed success, valid document with a different ID | field_mismatch |
Classification does not authorize a write or retry. Temporary maintenance remains an operation failure with its own evidence; follow the tool's documented recovery policy. A documented service-wide maintenance failure should stop a batch rather than trigger the same request for every row; a lone authorization error does not establish service-wide maintenance. If a write times out or its outcome is unknown, preserve that uncertainty and reconcile using a documented status/read-back mechanism before considering a retry. Never infer that a write failed, repeat it, or overwrite a document solely because a read failed or a returned field differs.
Cost Discipline
Track per task:
- model
- token estimate
- retries
- wall-clock time
- success/failure
Escalate model tier only when lower tier fails with a clear reasoning gap.