SkillVaultskills Browse all 500 skills

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

Platform Team Charter Advisor

Remove friction from scope definition and customer clarity with evidence, explicit trade-offs, and a verification plan.

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

Defines platform team scope, customers, and success measures so it does not become a ticket queue.

₹149 one-time

Get this skill archive

What this skill helps you do

  • Scope definition
  • Customer clarity
  • Success measures

How Platform Team Charter Advisor works

You provide

Schema, query plans, and the real access pattern

It inspects

Plan accuracy and lock behavior for scope definition

It decides

A customer clarity change weighed against write cost

You verify

Re-measured plan with buffer reads and timing compared

What it checks first

Platform Team Charter Advisor defines platform team scope, customers, and success measures so it does not become a ticket queue. Use it when the work involves Scope definition, Customer clarity, Success measures.

  1. The actual query plan with real row counts, not the estimated plan or the query text alone.
  2. Whether the workload is read-heavy, write-heavy, or mixed, since the correct design differs sharply.
  3. Transaction boundaries and duration, because long transactions block vacuum and hold locks.
  4. Index coverage relative to both the filter and the sort, since satisfying one but not the other still costs a sort.
  5. Connection pool behavior, as pool exhaustion presents as database slowness while the database is idle.

Failure modes it recognizes

  • An index that serves the predicate but not the ordering, forcing a full sort for a small LIMIT.
  • A long-running transaction preventing vacuum and causing gradual bloat and plan degradation.
  • Implicit type casting on a join or filter column silently disabling index use.
  • Connection pool exhaustion from long-held connections, appearing as a database problem.
  • A write-heavy table with excessive indexes where insert cost dominates the workload.
  • Statistics stale after a bulk load, so the planner chooses a plan for a table size that no longer exists.

Answers it will reject

  • Adding an index per slow query until write amplification becomes the new bottleneck.
  • Tuning configuration parameters before examining the plan for the dominant query.
  • Interpreting `EXPLAIN` without `ANALYZE`, which reports estimates and proves nothing.
  • Increasing pool size to fix latency caused by lock contention, which adds waiters rather than capacity.

Decision rules it applies

  • Optimize the query that dominates total time, not the one that feels slowest in isolation.
  • Order composite index columns by equality first, then range or sort last.
  • Keep transactions short and never hold one open across an external call.
  • Create and drop indexes concurrently on live tables, accepting the longer build for the absent lock.

Evidence it asks for

  • `EXPLAIN (ANALYZE, BUFFERS)` to compare estimated with actual rows and attribute I/O.
  • Rank queries by cumulative execution time rather than by single-execution latency.
  • Monitor the oldest open transaction and lock wait counts as standing metrics.

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

  • Scope definition current-state map
  • Customer clarity root-cause register
  • Success measures 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

Our platform team has become a ticket queue for every request nobody else wants. How do we fix the charter?

Expected output

A team without a defined product becomes a queue by default. Define the platform as a product with named internal customers, publish what is supported and what is not, and measure adoption and self-service rather than tickets closed...

Boundaries and compatibility

Ideal for

  • Scope definition: produce a decision or artifact grounded in supplied evidence.
  • Customer clarity: produce a decision or artifact grounded in supplied evidence.
  • Success measures: 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.