Agentic Engineering

affaan-m/ECC/pi/core/skills/agentic-engineering

by affaan-mef648e01899ba3e8dc6371642deaaf64b4477775No license275K starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated 4 days ago

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.

AI-generated overview

Guides agents through eval-first engineering workflows with task decomposition, model routing and cost tracking.

What it does
This skill provides operating guidance for engineering work carried out largely by AI agents, with humans enforcing quality and risk controls. It defines an eval-first loop, a 15-minute unit rule for task decomposition, model-tier routing by task complexity, session strategy, review priorities for AI-generated code, and per-task cost tracking. It produces process instructions rather than files or scripts.
When to use it
Use it when planning or executing engineering work that agents will carry out end to end. It fits situations where completion criteria, decomposition, evaluation and model selection need to be structured before implementation begins.
Requirements
No tools, packages, runtimes, credentials or network access are required; it is instructions only and ships no scripts.

Agentic Engineering

Use this skill for engineering workflows where AI agents perform most implementation work and humans enforce quality and risk controls.

Operating Principles

  1. Define completion criteria before execution.
  2. Decompose work into agent-sized units.
  3. Route model tiers by task complexity.
  4. Measure with evals and regression checks.

Eval-First Loop

  1. Define capability eval and regression eval.
  2. Run baseline and capture failure signatures.
  3. Execute implementation.
  4. 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.

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.

Source and attribution

Source:affaan-m/ECCinpi/core/skills/agentic-engineeringat commitef648e0

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal