SkillVaultskills Browse all 500 skills

Business Operations · Version 1.3.0 · Reviewed 2026-08-02

Developer Experience Auditor

Remove friction from loop measurement and friction identification with evidence, explicit trade-offs, and a verification plan.

4 method steps 5 documented failure modes 5 diagnostic checks 7 quality gates

Measures and improves the internal development loop from checkout to merged change.

₹99 one-time

Get this skill archive

What this skill helps you do

  • Loop measurement
  • Friction identification
  • Improvement ranking

How Developer Experience Auditor works

You provide

Obligations, data inventory, and current controls

It inspects

Requirement type and implemented control for loop measurement

It decides

A friction identification gap register with accountable owners

You verify

Each control mapped to evidence an auditor would accept

What it checks first

Developer Experience Auditor measures and improves the internal development loop from checkout to merged change. Use it when the work involves Loop measurement, Friction identification, Improvement ranking.

  1. Whether the obligation is a legal requirement, a contractual commitment, or an internal policy — the escalation path differs.
  2. The specific data categories and lawful basis, rather than a general statement about compliance.
  3. Data flows across jurisdictions and processors, which determine transfer obligations.
  4. Retention and deletion behavior in every downstream copy, including backups and analytics.
  5. Who is accountable for the decision, since a compliance analysis without an owner is not actionable.

Failure modes it recognizes

  • Deletion implemented in the primary store while copies persist in backups, exports, logs, and warehouses.
  • Consent collected for one purpose and reused for another without a valid basis.
  • A subprocessor added without a data-processing agreement or customer notification.
  • Retention policy defined but never enforced by an automated job.
  • A control documented in policy but not implemented in the system it describes.

Answers it will reject

  • Providing a definitive legal conclusion rather than a structured analysis for qualified review.
  • Treating a compliance certification as evidence that a specific control works.
  • Relying on contractual language to mitigate a technical risk that is technically preventable.
  • Presenting risk without severity, likelihood, and the accountable owner.

Decision rules it applies

  • Separate legal requirement, contractual obligation, and internal policy in every finding.
  • Escalate to qualified counsel for anything that constitutes legal advice, and say so plainly.
  • Map every obligation to a specific implemented control and its evidence, or mark it as a gap.
  • Prefer technical enforcement over documented intent, because documented intent is not a control.

Evidence it asks for

  • Build a data inventory: category, source, purpose, basis, location, retention, and downstream copies.
  • Trace one deletion request end to end and enumerate every store it must reach.
  • Record the evidence artifact that would satisfy an auditor for each control.

The method inside

  1. Map actual work and queues rather than the documented happy path
  2. Classify waits, rework, ownership gaps, and legitimate exceptions
  3. Identify the constraint producing the largest downstream effect
  4. Redesign the handoff with measurable entry and exit criteria

Deliverables

  • Loop measurement current-state map
  • Friction identification root-cause register
  • Improvement ranking future-state control plan

Evidence requirements

  • Process map, SOP, timestamps, exceptions, and work records
  • Owners, entry-exit criteria, SLAs, and system boundaries
  • Representative cases including failures and workarounds

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

New engineers say our development setup is painful but we cannot pin down what to fix.

Expected output

Measure the loop rather than collecting opinions: time from clone to running app, from change to feedback, and from open to merged. The dominant cost is usually local environment setup or slow feedback, and both are fixable once quantified...

Boundaries and compatibility

Ideal for

  • Loop measurement: produce a decision or artifact grounded in supplied evidence.
  • Friction identification: produce a decision or artifact grounded in supplied evidence.
  • Improvement ranking: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Automating a broken process without diagnosis
  • Treating every exception as employee noncompliance

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.