gh-implementation-plan

To generate a full-stack implementation plan, convert approved architecture specifications into detailed, layer-by-layer roadmaps covering database migrations, RLS policies, backend logic, and frontend components before code execution.

To enforce Row Level Security requirements, use strict safety gates that block progress until new tables have RLS policies explicitly approved, ensuring database schema security compliance before backend development begins.

Yes, you need an existing PRD, design direction, and Supabase schema to ensure technical alignment. The implementation plan requires integration with these architecture specifications to validate database migrations and frontend components.

The best way to prevent architectural drift is to enforce a mandatory, developer-reviewed implementation plan before writing code, ensuring database, backend, and frontend layers are strictly aligned with the approved architecture spec.

Yes, TypeScript strict mode can be enforced as a safety gate within the implementation planning workflow. It blocks progress until explicit approval is granted, ensuring frontend components meet strict type requirements before code execution.

Implementation plans block progress to prevent implementation errors. Safety gates require explicit developer approval for backend RPCs, database migrations, and frontend components, ensuring all layers are fully reviewed before any code is written.