What problem does it solve?
Extensibility decisions often create long-lived complexity and security risk when teams generalize too early, let extensions bypass invariants, or fail to version compatibility boundaries.
Core Features & Use Cases
- Extension point governance: Establishes when extension points are justified by proven variation and explicit ownership.
- Non-bypassable domain invariants: Defines rules that extensions must not circumvent (validation, authorization, tenant isolation, audit, and financial correctness).
- Versioned compatibility contracts: Specifies how extension interfaces and configs evolve with breaking-change policies and deprecation timelines.
- Security boundary & sandboxing: Requires explicit policies for network, filesystem, and database access, including SSRF and untrusted input handling.
- Validation & observability: Mandates strict schema validation for extension-supplied data and per-invocation tracing for debugging and incident response.
Quick Start
Use the extensibility-design skill to produce a guarded extension point plan for a new plugin interface, hook system, or configuration-driven provider mechanism in your product.