kvenkatrajan

Squad Charter: Eval-to-Action Loop -- Closing the loop between weekend compete runs and weekly engineering investments

Squad Charter: Eval-to-Action Loop -- Closing the loop between weekend compete runs and weekly engineering investments

Squad Charter: Eval-to-Action Loop -- Closing the loop between weekend compete runs and weekly engineering investments

Squad Charter: Eval-to-Action Loop -- Closing the loop between weekend compete runs and weekly engineering investments

Squad Charter: Eval-to-Action Loop -- Closing the loop between weekend compete runs and weekly engineering investments

kvenkatrajan

How May We Make the Weekly Eval Reporting Action-Driven Product Impact

The Problem

Every Monday, the team meets to review results from weekend compete runs -- CLI, Claude Code, and Codex CLI evaluated across Sonnet 4.6, Opus 4.7, and GPT 5.4. Today, this meeting is largely passive reporting: scores go up, scores go down, the team discusses possible reasons, and then disperses to work on whatever feels most promising.

What's missing is a closed loop:

Weekend Runs --> Identify Signals --> Select Investments --> Execute --> Validate

kvenkatrajan

Agent Trajectory Analysis — Design Overview

What is this?

A deterministic analysis pipeline that takes raw agent trajectory recordings (ATIF v1.6 format) and produces structured reports showing exactly what the agent did, how much it cost, and what went wrong.

ATIF trajectory.json → OTel spans → normalize → metrics + diagnostics + turns → reports → repo mapping → code fixes / sub-issues

kvenkatrajan

PR #2190 Analysis: azure-bya vs Existing Skills — Integration Map

Verdict: Hybrid — Keep BYA orchestrator + prereq as new skills, merge the rest into existing

---

What BYA Genuinely Adds (Not Present Today)

1. Source Code Prereq Scanning (azure-bya-prereq) — NEW SKILL

• Evaluates code readiness before any IaC work: build health, completeness, dependency compat

kvenkatrajan

Learn MCP → Skill Generator: A Docs-First Approach to Agent Skills

Brainstorm document — April 2026

The Problem

Agent skills today are agent-generated through user interaction and by service SMEs, producing agent-consumable markdown grounded in Microsoft Learn documentation. This works well for individual skills, but leads to inconsistencies in content coverage across services — some skills have deep SDK references and troubleshooting tables while others have minimal coverage. The Microsoft Learn MCP tools (microsoft_docs_search, microsoft_docs_fetch, microsoft_code_sample_search) already exist and return rich, structured content — but are inconsistently used in skill authoring today, with only a few skills leveraging them while most rely on manual knowledge capture.

The Idea

kvenkatrajan

Wiring OpenTelemetry in a VS Code Extension

A practical guide to adding telemetry to your VS Code extension -- covering setup, data captured, and PII handling.

---

What does this help with?

@vscode/extension-telemetry answers "what are my users doing and what's breaking?" It's built for product analytics and error monitoring -- the 80% case for extension authors.

kvenkatrajan

PR #1244 Review: azure-infra-planner skill

High-Level Suggestions

1. Rename to azure-enterprise-infra-planner

azure-prepare plans infrastructure by analyzing source code and mapping it to one of 5 host types (containerapp, appservice, function, staticwebapp, aks). It has no logic to plan the remaining 43 resource types in this skill — VNets, Firewalls, VPN Gateways, VMs, Service Bus, Key Vault, etc. It cannot look at a workload description and decide "you need a hub-spoke VNet with NSGs and a Firewall."

This skill fills that gap: infrastructure-first planning for platform engineers, where the input is a workload description (not code) and the output covers all 48 resource types. Renaming to azure-enterprise-infra-planner makes this distinction clear.

kvenkatrajan

Progressive Disclosure for MicrosoftDocs/Agent-Skills via azure-skills — single azure-docs skill design with 3-tier loading

Progressive Disclosure for MicrosoftDocs/Agent-Skills

Date: March 12, 2026 Problem: Agent-Skills has 193 service skills, each 100-850 lines. Loading them all is impossible. Loading even one full skill (e.g., Azure Functions at 366 lines / ~135 links) wastes tokens when the user only needs one category. Solution: Restructure Agent-Skills into a three-tier progressive disclosure model with a single router SKILL.md, per-service reference files, and on-demand Microsoft Learn fetching.

---

kvenkatrajan

azure-prepare: Progressive Disclosure Flow

Date: March 12, 2026 Scope: How azure-prepare uses recipes, runtimes, and service references through progressive disclosure Walkthrough prompt: "Create a Node.js Express API with Cosmos DB that I can deploy to Azure Container Apps"

---

1. What Is Progressive Disclosure in azure-prepare?

kvenkatrajan

azure-skills + MicrosoftDocs/Agent-Skills: Full Overlap Analysis

Date: March 11, 2026 Context: Beyond diagnostics/troubleshooting, where else do azure-skills and Agent-Skills overlap? What content from Agent-Skills should azure-skills reference?

---

1. Overlap Map Summary

There are 6 major overlap areas between azure-skills (24 operational skills) and MicrosoftDocs/Agent-Skills (193 service documentation skills):