gh-implementation-plan

Convert approved architecture specifications into layer-by-layer implementation plans.

Updated Jun 28, 2026

Search Tags:#workflow #planning #architecture #implementation #supabase #engineering

Ready to run

npx skills add https://github.com/Globaly-Inc/GH-AI-Skills-and-Plugins --skill gh-implementation-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gh-implementation-plan
Source: https://github.com/Globaly-Inc/GH-AI-Skills-and-Plugins/tree/main/skills/gh-implementation-plan
Command: npx skills add https://github.com/Globaly-Inc/GH-AI-Skills-and-Plugins --skill gh-implementation-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents architectural drift and implementation errors by enforcing a mandatory, developer-reviewed plan before any code is written, ensuring all layers—DB, backend, and frontend—are aligned.

Core Features & Use Cases

Layered Planning: Generates structured plans covering database migrations, RLS policies, backend RPCs, and frontend components.
Safety Gates: Enforces strict requirements like RLS on new tables and TypeScript strict mode, blocking progress until explicit approval.
Use Case: Before building a new user-facing feature, use this skill to generate a comprehensive implementation roadmap that ensures your database schema, API endpoints, and UI components are fully spec'd and reviewed.

Quick Start

Invoke the implementation plan skill to generate a step-by-step roadmap for the current architecture spec.

Frequently Asked Questions about gh-implementation-plan

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

FAQPage Schema

How do I generate a full-stack implementation plan from an approved architecture spec?▼

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.

How do I enforce Row Level Security requirements when planning new database tables?▼

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.

Do I need an existing Supabase schema and PRD before creating an implementation plan?▼

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.

What is the best way to prevent architectural drift during full-stack development?▼

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.

Can I use TypeScript strict mode as a safety gate in my implementation planning workflow?▼

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.

Why does my implementation plan block progress before backend RPCs are fully specified?▼

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.