feature-shipping-campaign

Sequences gated phases for shipping new features into a Next.js video portal.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/MarineTeam/fable-video --skill feature-shipping-campaign-marineteam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-shipping-campaign
Source: https://github.com/MarineTeam/fable-video/tree/main/.claude/skills/feature-shipping-campaign
Command: npx skills add https://github.com/MarineTeam/fable-video --skill feature-shipping-campaign-marineteam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping a new feature into the Marine Video Portal without breaking existing invariants requires coordinating architecture rules, change control, validation, environment config, documentation, and deployment — this Skill turns that into one ordered, gate-checked path so nothing gets skipped. ## Core Features & Use Cases - Decision-gated phases: Seven phases (scope, pre-flight, design, implement, validate, docs, ship) each ending in a GATE with expected output and an explicit if-not branch. - Design gate against architecture invariants: Written answers required for access tier, Redis key design, bunny.net cache invalidation, rate limiting, audit logging, and email handling before any code is written. - Routing to sibling skills: Sends docs-only edits, dependency bumps, bug fixes, and security responses to the correct specialized skill instead of over-applying the full process. - Use Case: When asked to add a new admin capability or API endpoint to the portal, the Skill walks you from done-criteria through lint/test baselines, a PR with pasted gate evidence, CI verification, and a post-deploy production smoke test. ## Quick Start Ask the assistant to add a new feature, endpoint, or admin capability to the Marine Video Portal and have it follow the feature-shipping-campaign phases from scoping through production verification.

Frequently Asked Questions about feature-shipping-campaign

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

FAQPage Schema
How do I add a new feature to a Next.js Pages Router app safely?

Follow a gated sequence: write done-criteria first, verify a clean baseline with lint and tests, answer design questions about access guards and data storage, implement in lib-to-API-to-UI order, then validate with computed test counts and manual smoke steps before merging.

When should I not use a full feature-shipping workflow?

Skip it for docs-only edits, pure dependency bumps, bug fixes restoring broken behavior, trivial self-contained tweaks, and security alert responses. Those route to lighter-weight processes like change-control, dependency-currency, or a debugging playbook instead.

What design questions should be answered before writing endpoint code?

Decide which auth guard enforces access, whether new Redis keys are needed, whether bunny.net mutations require cache invalidation, whether the endpoint needs rate limiting, and whether admin mutations need audit logging. Write the answers down before implementing.

Why is a merged PR not enough to consider a feature done?

Automated lint and unit tests only cover lib/ logic, not API routes or page behavior end to end. The feature is only done after CI is green, the Vercel deployment is live, and the manual smoke steps pass against the production URL.

Does adding an environment variable take effect after merging code?

No. Environment variable changes on Vercel only apply to new deployments, so after adding the variable you must trigger an explicit redeploy. Merging the PR alone does not activate the new variable.