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.
- License 许可
- MIT
- 最近更新
- 2026-11-11
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- agentic-engineering
- metadata
- { "origin": "ECC" }
- description
- 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.
03 SKILL.md 正文
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.okis 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.
04 同仓库更多 Skills
system-lifecycle-designer
Universal architectural methodology for designing granular, atomic, and sub-atomic lifecycles and end-to-end workflows for single functionality integrations across any domain (daemons, batch jobs, request transactions, resource pools). Provides patterns for deterministic identity, pre-commit validation, differential reconciliation, sticky leasing, state machines, transactional persistence, and closed-loop feedback.
style-sampling
Make a new episode in a proven video style - Collage Explainer, Finance Explainer, Animated Science Explainer, 3D Brand Explainer, 3D True Crime - on the person's topic. Use for "an episode of", "in the style of", "sample this style", 「用这个风格做一集」. One video to copy is reverse-any-video.
reverse-any-video
Rebuild any video file as an editable HyperFrames project - motion graphics, talking heads, live action or AI-generated footage - checked against the original frame by frame. Use to reverse, recreate, remake, replicate or copy a video, or 「复刻这个视频」「照着这个视频做一个」.
typescript-patterns
TypeScript patterns for strict, type-safe, maintainable code in modern TypeScript and JavaScript applications. Covers strict compiler configuration, type design, narrowing, discriminated unions, generics, async and error handling, module boundaries, dependency hygiene, and type-level testing. Use when writing or reviewing TypeScript or JavaScript code.
test-collaboration
Inventory and govern a project's test assets. Connect requirements, business rules, risks, bugs, and cross-boundary contracts to stable TEST-IDs and executable evidence in the repository's existing test registry or TESTS.md. Use for test inventory, test gap analysis, unit/integration/contract/E2E/smoke classification, bug-to-test regression protection, consumer/provider contract testing, test-necessity review, and pre-delivery evidence review.
story-lifecycle
Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira/Linear/Taiga but needs structured delivery tracking.