[Extension]: Add Roullout

Inizia individuando il catalogo delle estensioni e il formato delle voci esistenti, quindi confrontalo con la voce di catalogo Rollout proposta e con il manifest extension.yml menzionato qui. Convalida la modifica al catalogo eseguendo specify extension add rollout e verificando che i comandi e gli hook vengano registrati correttamente; l'attività è completata quando la voce Rollout è presente e l'installazione riesce.

Extension ID

rollout

Extension Name

Rollout

Version

0.1.2

Description

Progressive-delivery capability for Spec-Driven Development: teaches agents to recognize feature-flag / canary delivery candidates and fold a concrete rollout strategy into specs, plans, tasks, and implementation.

Author

Fyloss

Repository URL

https://github.com/Fyloss/spec-kit-rollout

Download URL

https://github.com/Fyloss/spec-kit-rollout/archive/refs/tags/v0.1.2.zip

License

MIT

Homepage (optional)

https://github.com/Fyloss/spec-kit-rollout

Documentation URL (optional)

https://github.com/Fyloss/spec-kit-rollout/tree/master/docs/

Changelog URL (optional)

https://github.com/Fyloss/spec-kit-rollout/blob/master/CHANGELOG.md

Required Spec Kit Version

=0.12.0

Required Tools (optional)

- Selected provider MCP server (e.g: Launchdarkly)

Number of Commands

9

Number of Hooks (optional)

7

Tags

feature-flags, progressive-delivery, canary-release, rollout, mcp, launchdarkly, release-management

Key Features

• Automatic rollout detection – Injects progressive-delivery doctrine at each Spec Kit phase (specify → clarify → plan → tasks → analyze → checklist → implement)
• Zero new commands – All functionality integrates into existing Spec Kit workflow via before_* hooks
• Self-gating hooks – Each phase checks for a rollout marker in spec.md; skips if not needed
• LaunchDarkly provider (V1) – Native support for LaunchDarkly feature flags
• MCP integration – One-time /speckit.rollout.connect setup wires LaunchDarkly MCP server

Testing Checklist

• Extension installs successfully via download URL
• All commands execute without errors
• Documentation is complete and accurate
• No security vulnerabilities identified
• Tested on at least one real project

Submission Requirements

• Valid extension.yml manifest included
• README.md with installation and usage instructions
• LICENSE file included
• GitHub release created with version tag
• All command files exist and are properly formatted
• Extension ID follows naming conventions (lowercase-with-hyphens)

Testing Details

• Install the extension with specify extension add rollout in a Spec Kit project → confirm it installs and validates cleanly, with all commands and hooks registered.
• Run /speckit.rollout.config with a LaunchDarkly MCP server already registered in your client → confirm you're walked through provider/project/environment selection and end up with a written config block, with no MCP command or credential stored anywhere.
• Run /speckit.specify Add a dark mode toggle in settings, controlled by a feature flag → check that spec.md gets a ## Delivery Considerations section naming a candidate boolean flag (e.g. dark-mode-enabled).
• Run /speckit.plan on the dark-mode spec → check that plan.md gets a ## Delivery Strategy section (flag name, phased rollout, targeting, telemetry gates, rollback conditions).
• Run /speckit.tasks → check that tasks.md gets concrete rollout tasks, including one to create the dark-mode-enabled flag in LaunchDarkly, plus configuring environments/targeting, integrating the SDK, adding telemetry, and defining rollback.
• Run /speckit.implement on the dark-mode feature with an MCP server registered and configured → confirm the dark-mode-enabled flag creation task is executed and the flag now exists in your LaunchDarkly project (check the LaunchDarkly dashboard or ask the agent to read the flag status back).

Example Usage

- Install the extension with `specify extension add rollout` in a Spec Kit project → confirm it installs and validates cleanly, with all commands and hooks registered.
- Run `/speckit.rollout.config` with a LaunchDarkly MCP server already registered in your client → confirm you're walked through provider/project/environment selection and end up with a written config block, with no MCP command or credential stored anywhere.
- Run `/speckit.specify Add a dark mode toggle in settings, controlled by a feature flag` → check that `spec.md` gets a `## Delivery Considerations` section naming a candidate boolean flag (e.g. `dark-mode-enabled`).
- Run `/speckit.plan` on the dark-mode spec → check that `plan.md` gets a `## Delivery Strategy` section (flag name, phased rollout, targeting, telemetry gates, rollback conditions).
- Run `/speckit.implement` on the dark-mode feature with an MCP server registered and configured → confirm the `dark-mode-enabled` flag creation task is executed and the flag now exists in your LaunchDarkly project (check the LaunchDarkly dashboard or ask the agent to read the flag status back).

Proposed Catalog Entry

{
  "rollout": {
    "name": "Rollout",
    "id": "rollout",
    "description": "Progressive-delivery capability for Spec-Driven Development: teaches agents to recognize feature-flag / canary delivery candidates and fold a concrete rollout strategy into spec kit workflow",
    "author": "Fyloss",
    "version": "0.1.2",
    "download_url": "https://github.com/Fyloss/spec-kit-rollout/archive/refs/tags/v0.1.2.zip",
    "repository": "https://github.com/Fyloss/spec-kit-rollout",
    "homepage": "https://github.com/Fyloss/spec-kit-rollout",
    "license": "MIT",
    "requires": {
      "speckit_version": ">=0.12.0"
    },
    "provides": {
      "commands": 9
    },
    "tags": ["feature-flags", "progressive-delivery", "canary-release", "rollout", "mcp", "launchdarkly", "release-management"],
    "verified": false,
    "downloads": 0,
    "stars": 0,
    "created_at": "2026-07-07T00:00:00Z",
    "updated_at": "2026-09-11T00:00:00Z"
  }
}

Additional Context

No response