supabase-build-planning

Plan and stage Supabase schema builds with pre-flight checks and approval gates.

Updated Aug 23, 2026

Search Tags:#planning #migration #supabase #governance #schemas #data-model

Ready to run

npx skills add https://github.com/zincdigitalofmiami/zinc-fusion-v16 --skill supabase-build-planning

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: supabase-build-planning
Source: https://github.com/zincdigitalofmiami/zinc-fusion-v16/tree/main/.kilo/skills/supabase-build-planning
Command: npx skills add https://github.com/zincdigitalofmiami/zinc-fusion-v16 --skill supabase-build-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plans and stages the Supabase schema build for ZINC Fusion V16 when data sources and contracts are evolving, turning ambiguity into a checkpointed, actionable plan.

Core Features & Use Cases

Pre-flight assessment and guided loops (source volatility, schema ownership, table contracts, migration slices) to coordinate cross-team work.
Canonical-plan governance with explicit decisions, provisional decisions, and migration slices to track progress and changes.
Safe handoff and implementation gating that avoids fake data and guarantees alignment with project truth.

Quick Start

Initiate pre-flight planning against the canonical migration plan and outline the first migration slice.

Frequently Asked Questions about supabase-build-planning

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

FAQPage Schema

How do I plan Supabase schema migrations when data sources are still evolving?▼

Supabase schema migration planning uses pre-flight assessments and guided loops to coordinate cross-team work, turning ambiguous data sources into a checkpointed, actionable plan with provisional decisions and migration slices.

What is the best way to stage Supabase database migrations to avoid using fake data?▼

Staging Supabase database migrations safely requires enforcing pre-flight checks and approval gates, guaranteeing alignment with project truth and canonical plans to avoid fake data during implementation handoffs.

How does canonical-plan governance work for Supabase schema builds?▼

Canonical-plan governance tracks Supabase schema builds through explicit decisions, provisional decisions, and migration slices, locking contracts and ensuring structured progress tracking across nine canonical schemas.

Can I use pre-flight checks to determine migration order for Supabase schemas?▼

Pre-flight checks assess source volatility, schema ownership, and table contracts to determine migration order, coordinating cross-team work before locking contracts for Supabase schema builds.

When do I need approval gates for Supabase schema revisions?▼

Approval gates are needed during Supabase schema revisions to enforce safe handoff and implementation gating, ensuring alignment with project truth and avoiding fake data before proceeding with migration slices.

Does schema migration planning work with nine canonical schemas in Supabase?▼

Schema migration planning applies directly to teams building or revising nine canonical schemas in Supabase, coordinating cross-team work through loop-based planning and canonical-plan references.