Use this skill when an AI agent is executing software development, code generation, refactoring, debugging, or system architecture tasks to enforce strict harness principles, self-verification gates, non-destructive editing, context collapse defense, and human-in-the-loop boundaries.
Use this skill when the user asks to create, draft, review, format, or generate a Pull Request (PR) title and description, specify target or source branches for a repository, or convert git branch diffs into concise, high-impact, non-AI-slop PR content.
Use this skill when explaining OpenTelemetry concepts, choosing telemetry signals, planning or reviewing Collector architectures and declarative configuration, operating or troubleshooting telemetry pipelines, securing telemetry data, evaluating zero-code instrumentation, or planning Prometheus, OpenCensus, or OpenTracing interoperability and migration. Do not use it to write language SDK/API instrumentation code or custom Collector components.
Use this skill when designing, evaluating, or implementing Agent workflows, prompt chains, routing, planning, reflection, multi-agent collaboration, memory management, or other framework-agnostic LLM orchestration patterns.
Use this skill when the user asks to improve AI-assisted development reliability, AGENTS.md, skills, tests, CI, hooks, review loops, agent workflow governance, loop engineering, agent automations, worktree isolation, maker/checker separation, or external state design for long-running agents. It designs feedforward guides, feedback sensors, verification gates, human decision points, and loop architectures from repository evidence.
Use this skill when the user wants to design, implement, review, or refactor software systems conforming to Clean Architecture principles. It structures code into Domain, Application, Infrastructure, and Presentation/API layers, enforcing inward-only dependencies. It advocates rich domain models, CQRS, and the Result pattern, operating on technology-neutral concepts without database or framework bindings.
Use this skill when the user asks to create, review, debug, or modernize Azure Pipelines YAML for CI/CD, especially .NET builds, Azure App Service deploys, or IIS/on-premises deploys. Prefer bundled templates and verify task syntax against Microsoft docs when version-specific accuracy matters.
Use this skill when the user gives vague, emotional, fragmented, screenshot-based, or complaint-style requirements and wants them converted into structured specs, acceptance criteria, or clarifying questions.