architecture-well-architected-commerce

Align cross-cutting VTEX commerce architecture decisions with pillar-based decision logs.

39|9|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/vtex/ai-skills --skill architecture-well-architected-commerce
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-well-architected-commerce
Source: https://github.com/vtex/ai-skills/tree/main/tracks/architecture/skills/architecture-well-architected-commerce
Command: npx skills add https://github.com/vtex/ai-skills --skill architecture-well-architected-commerce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-functional VTEX architecture decisions are often misaligned across teams, leading to inconsistent designs and elevated risk. This Skill provides a framework to scope, review, and document cross-cutting architecture work before implementation.

Core Features & Use Cases

  • Aligns decisions with the Well-Architected Commerce pillars: Technical Foundation, Future-proof, and Operational Excellence.
  • Routes decisions to appropriate product tracks (IO, Master Data, Marketplace) with documented rationale.
  • Produces concise decision logs detailing pillar coverage, native/OOTB vs IO/MD tradeoffs, and ownership to guide implementation and governance.

Quick Start

Run a cross-cutting VTEX architecture alignment for a project and generate a pillar-based decision log.

Frequently Asked Questions about architecture-well-architected-commerce

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I align cross-cutting VTEX commerce architecture decisions across multiple teams?▼

Align cross-cutting VTEX commerce architecture decisions by scoping and reviewing solutions against Well-Architected pillars. This framework produces decision logs with documented rationale, ownership, risks, and governance to ensure consistent designs across teams.

What is a well-architected commerce review for VTEX IO, Master Data, and marketplace tracks?▼

A well-architected commerce review evaluates cross-track technical planning across VTEX IO, Master Data, and marketplace tracks. It routes decisions to appropriate product tracks with documented pillar coverage and native versus custom tradeoffs.

How do I document VTEX architecture tradeoffs between native OOTB features and custom IO solutions?▼

Document VTEX architecture tradeoffs by generating decision logs that detail native OOTB versus IO or Master Data evaluation. Logs provide pillar-based justification, ownership, and risk assessment to guide implementation and governance.

When do I need a governance framework for VTEX architecture reviews?▼

You need a governance framework for VTEX architecture reviews when cross-functional decisions risk becoming misaligned across teams. It ensures solution scoping satisfies pillar-based justification and produces clear decision logs before implementation begins.

Does VTEX architecture alignment support Technical Foundation, Future-proof, and Operational Excellence pillars?▼

VTEX architecture alignment supports all three core Well-Architected Commerce pillars: Technical Foundation, Future-proof, and Operational Excellence. Decisions are explicitly mapped to these pillars to justify technical choices and governance outcomes.