gdd-rollout-status

Shows where a finished design cycle actually is in production rollout - unrolled / staging-only / canary-N% / prod-100% - by reading the feature-flag service (LaunchDarkly/Statsig/GrowthBook) via the rollout-coordinator. Surfaces STUCK rollouts (a canary that hasn't advanced for N days) and the design_arms outcome weighting. Read-only - GDD never advances or rolls back; it reports and notifies. Use after /gdd:ship to track the post-merge journey.

Jump to install

Repository: hegemonart/get-design-done
Last source activity: June 4, 2026 at 11:41
Detected SKILL.md language: English
Stars: 4
Forks: 1

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/hegemonart/get-design-done --skill gdd-rollout-status

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

get-design-done

Master design pipeline for Claude Code. 5-stage workflow: Brief → Explore → Plan → Design → Verify. Run 'brief' first in any new project to capture the design problem, then 'explore' to inventory the codebase and interview for context. Invoke without arguments for status and auto-routing.

2026-08-29

gdd-quick

Run the pipeline with optional agents skipped for speed. Skips: phase-researcher, design-assumptions-analyzer, design-integration-checker. Keeps: planner, executor, verifier, auditor. Activates for requests involving a lightweight design pass, a fast iteration, or a quick low-ceremony change.

2026-06-10

gdd-router

Routes a /gdd command to fast|quick|full path + S|M|L|XL complexity_class and returns {path, complexity_class, model_tier_overrides, resolved_models, estimated_cost_usd, cache_hits}. A SKILL.md prompt the model executes to emit a routing-decision JSON from rule tables (no separate agent spawn). Optional/advisory - invoked only by the skills that opt into routing; the budget-enforcer hook tolerates its absence. Read by hooks/budget-enforcer.ts.

2026-06-10

View all from this repository

/gdd:rollout-status

Closes the visibility gap after /gdd:ship: a PR merges, but staging → canary → 100% rollout happens outside GDD. This skill reports where each cycle's design actually is in production, by delegating to agents/rollout-coordinator.md (which reads the feature-flag service via the Phase 38 connections). Read-only - it reports + notifies; it never advances or rolls back a rollout. Contract + the <rollout_status> schema: ../../reference/rollout-coordination.md.

Invocation

Command

Behavior

/gdd:rollout-status

The current cycle's rollout state (from .design/STATE.md <rollout_status>, refreshed via the coordinator).

/gdd:rollout-status <cycle>

A specific cycle's rollout state.

/gdd:rollout-status --all

Every cycle with a <rollout_status> block - a rollout dashboard.

/gdd:rollout-status --stuck

Only the stuck rollouts (partial rollouts that haven't advanced for ≥ the threshold).

Steps

Probe the flag service. Check a flag connection is available (connections/launchdarkly.md / statsig.md / growthbook.md). None → print rollout-status: no flag service configured — connect one via /gdd:connections. and exit.

Delegate to rollout-coordinator (via Task): it reads the service, classifies via scripts/lib/rollout/rollout-status.cjs, refreshes the <rollout_status> block, and reports state + deployed % + stuck.

Render. Show each cycle: state · deployed_pct · last_changed · stuck?. For --stuck, list only stuck cycles with the days-since-change and an advance-or-rollback suggestion.

Do not act. Never run a flag-service mutation, advance a canary, or roll back - GDD reports; the human + the flag service decide.

Output

End with:

## ROLLOUT-STATUS COMPLETE