devenkhatri/everything-claude-code · Archived

agentic-engineering

Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing.

First seen Apr 6, 2026

Installation

$ npx skills add devenkhatri/everything-claude-code --skill agentic-engineering

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from devenkhatri/everything-claude-code · top by installs.

npx skills add devenkhatri/everything-claude-code

Browse all from devenkhatri/everything-claude-code

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

License LICENSE
Default branch main
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,731 B
  • docs SUMMARY.md 130 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

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.