feature-launch-gate

Verify Team OS repository launch artifacts before feature shipping.

32|16|Updated May 6, 2026
One-click install
npx skills add https://github.com/aakashg/product-growth-team-os --skill feature-launch-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-launch-gate
Source: https://github.com/aakashg/product-growth-team-os/tree/main/.claude/skills/feature-launch-gate
Command: npx skills add https://github.com/aakashg/product-growth-team-os --skill feature-launch-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents features from rolling out before the Team OS repository has the necessary PRD, decisions, analytics, queries, schemas, and feature-index updates so the launch is trackable, auditable, and reproducible.

Core Features & Use Cases

  • Pre-launch repo completeness checks: Ensures required product, engineering, design (when applicable), and data/analytics artifacts exist and meet content-quality rules.
  • Full vs. lightweight gating: Runs a strict major-launch checklist by default and a lighter advisory mode for small changes.
  • Analytics and schema validation: Enforces that metric definitions, canonical query file paths, SQL queries freshness, and table schema/data-catalog registration are correct—blocking on analytics failures in full mode and even in lightweight mode when analytics-relevant files are touched.

Quick Start

Run the feature launch gate for your feature by calling /feature-launch-gate {feature-name} before you ship.

Frequently Asked Questions about feature-launch-gate

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

FAQPage Schema
How do I block feature launches until repository documentation is ready?

Pre-launch readiness gating blocks feature launches by verifying that the Team OS repository contains complete and valid PRDs, decisions, and feature-index entries before the code ships. This ensures every rollout is trackable and auditable.

What is schema drift verification for analytics launch readiness?

Schema drift verification enforces that metric definitions, canonical query paths, SQL freshness, and table schemas match the data catalog. This analytics gate blocks launches when data-catalog inconsistencies are detected.

Can I run a lightweight advisory check for small feature rollouts?

Yes, you can run a lightweight advisory mode for smaller change rollouts instead of the strict major-launch checklist. It still enforces analytics-specific rules when analytics-relevant files are touched.

How do I validate PRD and SQL query files before shipping a feature?

PRD validation and SQL verification check required file existence and content quality in the repository. The gate enforces that metric definitions contain resolvable canonical query paths and verified SQL queries before launch.

Does launch readiness gating work without external dependencies?

Yes, feature launch gating operates directly on the Team OS repository without external dependencies. It applies content checks to local files to ensure product, engineering, and data artifacts are complete.