vellum-feature-flag-rollout

Guides feature flag changes and rollout hygiene for the Vellum Assistant codebase.

1.2k|166|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/vellum-ai/vellum-assistant --skill vellum-feature-flag-rollout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vellum-feature-flag-rollout
Source: https://github.com/vellum-ai/vellum-assistant/tree/main/.cursor/skills/vellum-feature-flag-rollout
Command: npx skills add https://github.com/vellum-ai/vellum-assistant --skill vellum-feature-flag-rollout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Feature flag changes in the Vellum Assistant codebase require consistent registry declarations, safe defaults, coordinated platform-side Terraform provisioning, and disciplined rollout practices. This Skill encodes those rules so flag additions, renames, removals, and reviews follow the same checklist every time.

Core Features & Use Cases

  • Flag Registry Enforcement: Ensures new flags use kebab-case keys, scope: "assistant", safe defaults, and declaration in meta/feature-flags/feature-flag-registry.json.
  • Rollout Hygiene Rules: Blocks new release-note migrations (the workspace-bulletin mechanism was removed) and restricts permission-controls-v2 from adding new deterministic approval modes.
  • Structured Review Workflow: Walks reviewers through registry checks, default behavior, docs leaks, platform Terraform updates, and focused test recommendations.
  • Use Case: When reviewing a PR that adds a rollout-gated assistant behavior, use this Skill to verify the flag key format, confirm the companion vellum-assistant-platform PR exists, and produce PR notes covering default state and rollout plan.

Quick Start

Review this pull request that adds a new assistant feature flag and check it against the rollout and registry rules.

Frequently Asked Questions about vellum-feature-flag-rollout

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

FAQPage Schema
How do I add a new feature flag to the Vellum Assistant?

Declare the flag in meta/feature-flags/feature-flag-registry.json with a kebab-case key, scope set to assistant, and a safe default. Add tests or guard coverage if resolver behavior changes, and open a companion vellum-assistant-platform PR to provision the flag in Terraform.

What should a feature flag code review check?

Confirm whether the change adds, renames, removes, or consumes a flag, then verify registry declaration, key format, default behavior, and rollout safety. Also check docs and user-facing copy for flag leaks, platform Terraform needs, and focused tests for resolver, route, or UI changes.

Can I add release notes for a flagged feature in Vellum Assistant?

No. The workspace-bulletin feature was removed and historical release-note migrations are frozen, so no new release-note migrations should be added for any feature. User-facing notes require designing an explicit on-demand surfacing mechanism first.

What approval modes are allowed under permission-controls-v2?

Only the conversation-scoped host computer access gate is permitted for assistant-owned actions. Do not add global toggles, persistent trust-rule UI, wildcard scopes, or time-window approvals.

What naming format do assistant feature flags require?

Assistant feature flags must use canonical kebab-case keys declared in the feature flag registry with scope set to assistant. Each new flag also needs a safe default value.