agentic-engineering

Guides AI-agent engineering workflows using eval-first execution, task decomposition, and model routing.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Femad-6/my-skills --skill agentic-engineering-femad-6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentic-engineering
Source: https://github.com/Femad-6/my-skills/tree/main/.github/skills/agentic-engineering
Command: npx skills add https://github.com/Femad-6/my-skills --skill agentic-engineering-femad-6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When AI agents perform most implementation work, teams lack a disciplined process for defining completion criteria, verifying output quality, and controlling model costs. This Skill provides an operating framework for agentic engineering so humans can enforce quality and risk controls over AI-generated code. ## Core Features & Use Cases - Eval-First Loop: Define capability and regression evals, capture baseline failure signatures, then re-run evals after implementation to compare deltas. - Task Decomposition: Apply the 15-minute unit rule so each work unit is independently verifiable with a single dominant risk and a clear done condition. - Model Routing & Cost Discipline: Route tasks across Haiku, Sonnet, and Opus tiers by complexity, and track model, tokens, retries, and success rates per task. - Use Case: A team delegating a multi-file refactor to an AI agent uses this Skill to split the work into verifiable units, assign Sonnet for implementation and Opus for architecture review, and validate results with regression evals before merging. ## Quick Start Use the agentic-engineering skill to plan and execute my next AI-assisted implementation task with eval-first verification and model routing.

Frequently Asked Questions about agentic-engineering

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure AI agent coding tasks for reliable results?

Decompose work into 15-minute units where each unit is independently verifiable, has a single dominant risk, and exposes a clear done condition. Define completion criteria before execution so agent output can be checked objectively.

What is eval-first development for AI-generated code?

Eval-first development defines a capability eval and a regression eval before implementation, runs a baseline to capture failure signatures, then re-runs evals after implementation to compare deltas. This verifies agent output against measurable criteria.

When should I use Haiku vs Sonnet vs Opus for coding tasks?

Use Haiku for classification, boilerplate transforms, and narrow edits; Sonnet for implementation and refactors; Opus for architecture, root-cause analysis, and multi-file invariants. Escalate tiers only when a lower tier fails with a clear reasoning gap.

What should I prioritize when reviewing AI-generated code?

Prioritize invariants and edge cases, error boundaries, security and auth assumptions, and hidden coupling or rollout risk. Skip style-only disagreements when automated format and lint tools already enforce style.

When should I start a fresh AI coding session versus continue one?

Continue the session for closely-coupled units, but start fresh after major phase transitions. Compact context after milestone completion rather than during active debugging to preserve diagnostic state.