Catalog
affaan-m/agentic-engineering

affaan-m

agentic-engineering

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.

NewUpdated Sep 9, 2026

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.

Files1
1 files · 1.0 KB

Select a file to preview

Overall Score

72/100

Grade

B

Good

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

85

Quality

68

Clarity

76

Completeness

58

Summary

This skill provides a framework for agentic engineering workflows where AI agents perform implementation while humans maintain quality control. It prescribes eval-first execution, task decomposition into 15-minute units, cost-aware model routing (Haiku/Sonnet/Opus), and review strategies tailored to AI-generated code. The skill operates as a meta-guidance system for planning and orchestrating multi-agent engineering processes.

Detected Capabilities

process-planningtask-decompositioncost-estimationmodel-selectioneval-definitioncode-review-guidancequality-gating

Trigger Keywords

Phrases that agents use to match this skill to user intent.

agentic engineeringagent task decompositioneval-first workflowmodel routingcost-aware ai executionai code review strategy

Use Cases

  • Plan and execute large engineering projects with agent-driven implementation
  • Route AI agent work across model tiers based on task complexity
  • Establish eval-based quality gates for AI-generated code before human review
  • Decompose complex engineering work into independently verifiable agent tasks
  • Implement cost-aware workflows that balance model capability with token budgets
  • Design code review processes that focus on invariants and security rather than style

Quality Notes

  • Strength: Clear operating principles with concrete structure (eval-first loop, task decomposition rules, model routing)
  • Strength: Practical 15-minute unit rule provides actionable guidance for breaking down work
  • Strength: Model routing guidance is specific and justified (Haiku for classification, Sonnet for implementation, Opus for architecture)
  • Strength: Session strategy offers pragmatic guidance for managing agent context and costs
  • Strength: Review focus section targets high-value code review areas rather than style minutiae
  • Weakness: Skill lacks concrete examples of eval definitions or failure signatures—guidance remains abstract
  • Weakness: No example decomposition of a real engineering project to illustrate principles
  • Weakness: Cost tracking recommendations are listed but lack detail on how to measure or report metrics
  • Weakness: Missing edge cases or failure scenarios—when does eval-first approach break down?
  • Weakness: No discussion of multi-agent coordination, dependency management, or inter-task sequencing
  • Weakness: Session strategy is high-level; lacks specific criteria for deciding 'major phase transitions'
Model: claude-haiku-4-5-20251001Analyzed: Sep 9, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

  1. v2.0

    Contract changed: description

    ✦ AIExpands activation context: adds explicit guidance for agents to use when planning or executing engineering work end to end.

    triggering2026-09-09

    LATEST
  2. v1.2

    Content updated

    ✦ AINo observable behavioral changes in skill instructions or supporting files.

    2026-07-14

    View This Version
  3. v1.1

    Content updated

    ✦ AIAdds LICENSE file.

    2026-04-20

    View This Version
  4. v1.0

    Seeded from github.com/affaan-m/everything-claude-code

    2026-03-16

    View This VersionInitial version

Use affaan-m/agentic-engineering in your dev environment

Command Palette

Search for a command to run...