product-foundationslisted

The foundational concerns every product must decide — users & operators, observability, audit logs, change logs, background processes, data retention & PII, notifications, runtime settings, rate limiting. Elicited defaults distilled from the 95octane reference implementation. Used by /vwf:architecture (the foundations checklist) and /vwf:blueprint (expanding accepted foundations into contracts); read the reference matching the foundation being decided or expanded.
virajp/ai-plugins · ★ 1 · AI & Automation · score 72

Install: claude install-skill virajp/ai-plugins

# Product Foundations Nine concerns every product hits sooner or later. Each has a **default contract** distilled from the 95octane reference implementation — proposed per product, never silently assumed: `/vwf:architecture` walks this checklist as part of its cross-cutting elicitation (one MCQ per foundation: **accept the default / adapt it / not applicable**), records the selection as a `cross_cutting` token, and `/vwf:blueprint` expands accepted ones into the canonical contract in `conventions.md` plus the per-entity surfaces each reference names. These are **elicited defaults**, not enforced standards: declining one is a recorded decision (the registry simply omits the token), not an `enforcement:` opt-out. The contract layer here is code-independent; each reference points at the reference-stack docs for the 95octane realization. ## The checklist | Foundation | Default (one line) | Reference | | -------------------- | -------------------------------------------------------------------------- | ---------------------------------------------------------- | | Users & operators | Two user classes; document-based RBAC; claims for account-status only | [users](references/users.md) | | Observability | OpenTelemetry (traces+metrics+logs) → Grafana Cloud, trace-correlated logs | [observability](references/observability.m