From ucp-agentic-commerce
Implements UCP Fulfillment extension for shipping/pickup methods, destinations, groups, selectable options, and estimated delivery in checkouts.
npx claudepluginhub orcaqubits/agentic-commerce-skills-plugins --plugin ucp-agentic-commerceThis skill is limited to using the following tools:
**Fetch live spec**: Web-search `site:ucp.dev specification fulfillment` and fetch the page for the exact fulfillment schema, method types, group structure, and configuration options.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Automates semantic versioning and release workflow for Claude Code plugins: bumps versions in package.json, marketplace.json, plugin.json; verifies builds; creates git tags, GitHub releases, changelogs.
Fetch live spec: Web-search site:ucp.dev specification fulfillment and fetch the page for the exact fulfillment schema, method types, group structure, and configuration options.
Fulfillment extends dev.ucp.shopping.checkout. It is pruned from negotiation if the Checkout capability is not in the intersection. Declared as "extends": "dev.ucp.shopping.checkout" in the schema.
shipping or pickup. Each method is tied to specific line items via line_item_ids.fulfillable_on indicating availability ("now" or an ISO date).The fulfillment extension has two configuration scopes:
platform_config (set by the platform, describes platform-level behavior):
supports_multi_group: Whether the platform supports handling multiple fulfillment groups/shipmentsmerchant_config (set by the merchant/business, describes business-level behavior):
allows_multi_destination: Whether multiple shipping addresses are supported (per method type)allows_method_combinations: Which method types can be combined (e.g., [["shipping", "pickup"]])ready_for_completeFetch the exact current schema from the live spec before implementing. The fulfillment data model has nested structures (methods → destinations → groups → options) that evolve across spec versions.
Also check the sample server at https://github.com/Universal-Commerce-Protocol/samples for reference fulfillment implementation.