agentic-engineering — Claude Code skill: what it does, how to install
Establishes protocols for agent-led workflows: breaks work into 15-minute verifiable units, enforces eval-first testing, and routes tasks between Haiku, Sonnet, and Opus.
npx skills add affaan-m/ECC --skill agentic-engineering -a claude-codeWhat agentic-engineering does
This skill sets up an execution framework where agents write code while developers control boundaries and risk. Work is split using the 15-minute unit rule. Each unit must be independently verifiable, focus on a single dominant risk, and declare a clear done condition. The eval-first loop executes regression checks before code changes, capturing failure signatures before verifying the final delta.
Workloads follow strict model routing to protect budgets. Haiku handles classification and narrow edits, Sonnet takes implementation and refactors, while Opus tackles system architecture and invariant tracking. Escalation happens only when a smaller model hits a visible reasoning wall. Teams track tokens, retries, and wall-clock duration per step.
Install this if your agent loses context on multi-file features or burns quota on trivial chores. For small, single-file scripts, it adds unnecessary overhead.
What it helps with
- Break complex refactors into 15-minute verifiable steps
- Capture baseline failure signatures before code generation
- Route tasks between Haiku, Sonnet, and Opus based on complexity
- Track token usage, retries, and wall-clock execution time
Example prompts for the agent
- Break this task into 15-minute units following agentic-engineering and start with evals
- Plan the authentication refactor using the eval-first approach
- Route this implementation ticket to the appropriate model tier per agentic-engineering
How to install agentic-engineering
1Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill agentic-engineering -a claude-code2Manually: put the files in place
~/.claude/skills/agentic-engineering/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/agentic-engineering/
1Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill agentic-engineering -a codex2Manually: put the files in place
.agents/skills/agentic-engineering/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill agentic-engineering -a cursor2Manually: put the files in place
.cursor/skills/agentic-engineering/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install affaan-m/ECC agentic-engineering2Manually: put the files in place
.github/skills/agentic-engineering/SKILL.md1Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill agentic-engineering -a gemini-cli2Platform CLI
gemini skills install https://github.com/affaan-m/ECC --path skills/agentic-engineeringManually: put the files in place
.devin/skills/agentic-engineering/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill agentic-engineering -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set146
The whole set →Similar
Questions about agentic-engineering
How do I install agentic-engineering in Claude Code?
Run npx skills add affaan-m/ECC --skill agentic-engineering -a claude-code. The rule file will be placed in ~/.claude/skills/agentic-engineering/SKILL.md.
What is the purpose of agentic-engineering?
It structures autonomous development by requiring agents to define completion criteria, run baseline tests before coding, and split tasks into short increments.
When does the skill escalate to a higher model tier?
Escalation to Sonnet or Opus occurs only when a lower tier fails because of a clear reasoning gap, preventing wasted spend on simple classification or edits.
Source text
SKILL.md · MIT
--- name: agentic-engineering 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. metadata: origin: ECC --- # 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.
© affaan-m · MIT · affaan-m/ECC