agentic-engineering

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

2|Updated May 30, 2026
One-click install
npx skills add https://github.com/virahitvin8/crafty-gis --skill agentic-engineering-virahitvin8
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentic-engineering
Source: https://github.com/virahitvin8/crafty-gis/tree/main/GIT_STAR/.agent/skills/agentic-engineering
Command: npx skills add https://github.com/virahitvin8/crafty-gis --skill agentic-engineering-virahitvin8

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 unreliable results 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: Break work into 15-minute, independently verifiable units, each with a single dominant risk and a clear done condition. - Cost-Aware Model Routing: Assign Haiku to narrow edits, Sonnet to implementation, and Opus to architecture and root-cause analysis, escalating tiers only on clear reasoning gaps. - Use Case: A team lead asks an agent to refactor a multi-module service; the skill structures the work into verifiable units, routes each unit to the right model tier, and validates results with regression evals. ## Quick Start Use the agentic-engineering skill to plan and execute my next refactoring task 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 effectively?

Define completion criteria before execution, decompose work into 15-minute independently verifiable units, and run an eval-first loop: baseline evals, implement, then re-run evals and compare deltas to catch regressions.

How to choose between Haiku, Sonnet, and Opus for coding tasks?

Route by task complexity: Haiku for classification and narrow edits, Sonnet for implementation and refactors, Opus for architecture and multi-file root-cause analysis. Escalate tiers only when a lower tier fails with a clear reasoning gap.

What should I review in AI-generated code?

Prioritize invariants, 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 agent session?

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.

How do I control costs when using AI coding agents?

Track model, token estimate, retries, wall-clock time, and success or failure per task. Use the cheapest capable model tier first and escalate only on demonstrated reasoning gaps rather than defaulting to the largest model.