Can I vibe code QPilot?

Build an off-site subscription and order scheduling engine for a WooCommerce store using Node.js, Express, Supabase, and Stripe. 1. DATA MODEL: Create tables for stores (id, woo_url, api_keys), customers (id, woo_customer_id, stripe_customer_id), subscription_schedules (id, customer_id, items_json, frequency_interval, next_run_at, status, failure_count), and execution_logs (id, schedule_id, status, error_message, woo_order_id). 2. CORE SCHEDULER: Implement a background worker using node-cron or Agenda that queries due active subscription_schedules every 5 minutes where next_run_at is past. Lock rows during execution to prevent race conditions. 3. PAYMENT & ORDER GENERATION: For each due schedule, trigger a charge using Stripe PaymentIntents off-session using stored customer tokens. Upon successful payment, send a POST request to the WooCommerce REST API endpoint (/wp-json/wc/v3/orders) to generate the pending processing order. Include line items, billing/shipping addresses, and transaction IDs. Update next_run_at based on frequency_interval. 4. RETRY LOGIC & FAILURE HANDLING: If the Stripe payment fails, increment failure_count, schedule a retry in 48 hours, and email the customer a payment update link. If payment fails 3 consecutive times, mark subscription_schedule status as 'paused'. If the WooCommerce REST API call fails after payment, log the failure alert to admin and retain the payment reference to prevent re-charging. 5. CUSTOMER PORTAL & WEBHOOKS: Expose API routes for customer management (pause, resume, update frequency, skip next shipment) and verify Stripe payment method update webhooks. OUT OF SCOPE: Multi-gateway tokenization outside Stripe, complex multi-currency tax engines, legacy WP-Cron dependencies.

$ each button prefixes agent-specific run instructions · build your own product, never copy proprietary code, trademarks or designs