Agents & OrchestrationSûr100100/100
agentic-engineering
Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing.
ou envoie-le directement à ton agent.
Installer dans ton projet
$ npx arboris-cli install agentic-engineeringContenu à copier
--- name: agentic-engineering description: Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing. 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.
Colle ce Markdown dans ton agent ou utilise les boutons ci-dessus pour l’écrire dans ton projet.
Ce que fait agentic-engineering
each unit should be independently verifiable
each unit should have a single dominant risk
each unit should expose a clear done condition
Haiku: classification, boilerplate transforms, narrow edits
Comment utiliser agentic-engineering
1
Copie le prompt
Un clic copie le prompt packagé (ou l'envoie à ton agent).
2
L'agent installe le skill
Il ajoute le SKILL.md et ses ressources à ton projet.
3
Activation automatique
Le skill s'active dès que le contexte correspond.
Déclencheurs pour agentic-engineering
Dis simplement à ton agent quelque chose comme :
Applique le skill agentic-engineering à cette tâche
Utilise agentic-engineering pour améliorer cette implémentation
Passe en revue ce sujet avec agentic-engineering
Skills liés à agentic-engineering
acceleration__microsoft-aibast-agents-library__solutions-deal-progression-manual-skills-4c8a74dab5dd
Compare synthetic acceleration options and clearly separate scenario value from forecast commitments.account-overview__microsoft-aibast-agents-library__solutions-account-intelligence-manual-skills-3546ce8f6420
Create a synthetic Acme account overview and identify evidence that merits seller attention.acroform-writer__microsoft-cat-agent-skills__submissions-e44ef69423b5
Use this skill whenever the user wants values written INTO an existing PDF form that lives in the connected SharePoint knowledge source — filling out, completing, populating, or submitting a fillable PDF (application, intake sheet, contract, government form) from data they supply, a spreadsheet row, or the conversation. Triggers include "fill out the job application form", "complete the intake form for [person]", "populate our standard NDA template", and "make this ready to send / non-editable" (flatten). The source form should be found via knowledge search; only ask the user to upload it if knowledge search turns up nothing plausible. different task), and do NOT use it on scanned/image-only PDFs that have no real fillable fields — those need OCR or manual overlay instead, which this skill explicitly detects and reports rather than silently failing.