agentic-engineering

Orchestrates AI agent implementation workflows using eval-first loops, task decomposition, and model routing.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/freedom909/real-estate-saas --skill agentic-engineering-freedom909
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agentic-engineering
Source: https://github.com/freedom909/real-estate-saas/tree/main/.trae/skills/agentic-engineering
Command: npx skills add https://github.com/freedom909/real-estate-saas --skill agentic-engineering-freedom909

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering teams delegating implementation work to AI agents often lack a disciplined process for defining completion criteria, verifying output quality, and controlling model costs, leading to unreviewed code and wasted tokens. ## Core Features & Use Cases - Eval-First Execution: Define capability and regression evals before implementation, capture baseline failure signatures, and compare deltas after changes. - 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. - Cost-Aware Model Routing: Route tasks by complexity across Haiku (classification, narrow edits), Sonnet (implementation, refactors), and Opus (architecture, root-cause analysis), escalating tiers only on clear reasoning gaps. - Use Case: When refactoring a multi-module service with AI agents, decompose the work into verifiable units, run baseline evals, assign Sonnet to implementation units, and review only invariants, error boundaries, and auth assumptions. ## Quick Start Ask the agent to plan and execute your next engineering task using the agentic-engineering workflow with eval-first verification and tiered 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 workflows for quality?▼

Define completion criteria before execution, decompose work into independently verifiable units, and run capability and regression evals before and after implementation. Compare eval deltas to confirm the change improved behavior without regressions.

What is eval-first development for AI agents?▼

Eval-first development means writing capability and regression evals before any implementation begins. You run a baseline to capture failure signatures, execute the implementation, then re-run evals and compare deltas to verify progress.

How do I choose between Haiku, Sonnet, and Opus for coding tasks?▼

Route by task complexity: Haiku handles classification, boilerplate transforms, and narrow edits; Sonnet handles implementation and refactors; Opus handles 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 tooling already enforces style.

When should I start a fresh AI agent session versus continue?▼

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

How do I control costs when AI agents write most of the code?▼

Track model, token estimate, retries, wall-clock time, and success or failure per task. Start with the lowest capable model tier and escalate only when the lower tier demonstrates a clear reasoning gap.