Agent skill
agentic-engineering
Operate as an agentic engineer — eval-first execution, task decomposition, cost-aware model routing (Haiku/Sonnet/Opus). Use when setting up AI-assisted workflows or optimizing model routing.
Install this agent skill to your Project
npx add-skill https://github.com/xbklairith/kisune/tree/main/dev-workflow/skills/agentic-engineering
SKILL.md
Agentic Engineering
Engineering workflows where AI agents perform most implementation and humans enforce quality and risk controls.
When to Activate
- Setting up AI-assisted development workflows
- Planning agent task decomposition
- Optimizing model selection for cost/quality
- Reviewing AI-generated code
Operating Principles
- Define completion criteria before execution
- Decompose work into agent-sized units
- Route model tiers by task complexity
- Measure with evals and regression checks
Eval-First Loop
- Define capability eval and regression eval
- Run baseline and capture failure signatures
- Execute implementation
- Re-run evals and compare deltas
Task Decomposition
Apply the 15-minute unit rule:
- Each unit independently verifiable
- Each unit has a single dominant risk
- Each unit exposes a clear done condition
Model Routing
| Tier | Use For | Cost |
|---|---|---|
| Haiku | Classification, boilerplate, narrow edits | Lowest |
| Sonnet | Implementation, refactors | Medium |
| Opus | Architecture, root-cause analysis, multi-file invariants | Highest |
Escalate model tier only when lower tier fails with a clear reasoning gap.
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
Skip: Style-only disagreements when automated format/lint already enforces style.
Cost Discipline
Track per task:
- Model used
- Token estimate
- Retries
- Wall-clock time
- Success/failure
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
e2e-testing
Playwright E2E testing — Page Object Model, configuration, flaky test strategies, and CI/CD integration. Use when writing, debugging, or configuring E2E tests.
brainstorming
Collaborative refinement of rough ideas into clear requirements/designs through systematic questioning. Use when requirements are vague or exploring architectural options.
test-driven-development
Strict RED-GREEN-REFACTOR enforcement with no exceptions. Use when implementing features or fixing bugs. No production code without a failing test first.
api-design
REST API design patterns — resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting. Use when designing, reviewing, or documenting API endpoints.
spec-driven-planning
MANDATORY planning — creates specs in docx/features/ with EARS requirements and technical design. MUST activate instead of ad-hoc planning for any new feature.
review
25-point code quality checklist covering structure, errors, security, performance, and testing. Use before commits or when reviewing code.
Didn't find tool you were looking for?