magnus919_agent-skills/api-design-and-evolution/templates/api-landscape-assessment.md

API Landscape Assessment

Scope And Decision

• Assessment date, scope, and evidence sources:
• Decision or problem this assessment must support:
• Accountable product, API, platform, security, and architecture owners:
• Known evidence gaps and confidence:

Inventory

Surface	Capability/authority	Audience/exposure	Style and contract	Lifecycle	Owner/contact	Consumers	Evidence/gaps

Coherence And Discoverability

• Shared domain concepts and authoritative owners:
• Duplicates, wrappers, forks, shadow surfaces, or intentional overlap:
• Rationale for keeping or consolidating each overlap:
• Catalog, contract, examples, support path, and lifecycle links:
• Search failures, stale records, undocumented consumers, or unowned surfaces:

Lifecycle And Governance

• New/change intake and decision locality:
• Baseline standards and risk factors that increase review depth:
• Exceptions, compensating controls, owner, and review condition:
• Consumer feedback, reliability, adoption, support, and compatibility evidence:
• Deprecation successor, migration support, telemetry, sunset criteria, and pause path:
• Retirement evidence, residual dependency check, communication, and recovery path:

Topology And Failure Boundaries

• North-south, east-west, ingress, and egress flows:
• Gateway/ingress responsibilities and owner:
• Mesh/service-to-service responsibilities and owner:
• Routing, identity, policy, transformation, retry, timeout, and limit placement:
• Observability and correlation at each boundary:
• Failure behavior, fail-open/closed choices, ambiguous completion, and rollback:

Findings And Actions

Priority	Finding/evidence	Consumer or operational impact	Action	Owner	Due condition/status

Verdict

• Landscape status: coherent, conditional, blocked, or incomplete:
• Decisions approved and decisions escalated:
• Required contract, platform, product, security, or architecture handoffs:
• Reassessment trigger: