Menu
Feature flag lifecycle management. Create, roll out, audit, and retire flags. Maintains flag manifest. Rollout gated on declared conditions.
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.
Based on SOC occupation classification
| name | flag |
| description | Feature flag lifecycle management. Create, roll out, audit, and retire flags. Maintains flag manifest. Rollout gated on declared conditions. |
Feature flags enable safe deployment of incomplete or risky features. You manage the full flag lifecycle: creation, rollout, audit, and retirement. A flag not in the manifest does not exist as far as this framework is concerned.
Manages feature flags through four modes: --create, --rollout, --audit, --retire. Maintains .wabblespec/flags/manifest.json as the authoritative flag registry. Writes flag receipt per operation.
--create | --rollout | --audit | --retire.wabblespec/flags/manifest.json — read and update)Validate flag ID is unique in manifest. Write entry with state DRAFT. Fields required: id, owner, description, created_at, state: DRAFT. Do not activate at creation — flags start DRAFT.
Read current flag state. Apply rollout gate (rules/rollout-gate.md). Gate must pass before state transitions: DRAFT → ACTIVE or ACTIVE → ROLLING. Write updated state to manifest.
ROLLING = gradual percentage-based exposure. Requires rollout_percentage and rollout_target fields.
Scan manifest for: DRAFT flags older than 30 days (stale), ROLLING flags with no rollout_percentage update in 14 days (stuck), ACTIVE flags with no associated task card (orphaned), flags with no owner. Report each with recommended action.
Transition state to RETIRED. Record retired_at timestamp and retirement_reason. Retired flags remain in manifest — do not delete. Deletion requires an explicit --purge flag (not default).
| Situation | Reference |
|---|---|
| Flag receipt write | engine/shared/references/script-delegation-contract.md → receipt-writer.py --type generic for the base, then --extra-json for the module-specific fields defined in schemas/flag-receipt.schema.json |
flag-receipt.json (.wabblespec/state/receipts/flag-receipt-<timestamp>.json):
{
"mode": "create | rollout | audit | retire",
"flag_id": "string",
"previous_state": "DRAFT | ACTIVE | ROLLING | RETIRED | null",
"new_state": "DRAFT | ACTIVE | ROLLING | RETIRED",
"rollout_gate_passed": "boolean — null if mode != rollout",
"flag_manifest_path": ".wabblespec/flags/manifest.json"
}
DRAFT → ACTIVE (rollout gate passed, manual promotion)
ACTIVE → ROLLING (rollout gate passed, percentage < 100%)
ROLLING → ACTIVE (100% rollout confirmed)
Any → RETIRED (explicit retire command)
Standalone adversarial analysis module. Generates the strongest honest case against an artifact or decision. Invokable directly by any caller — not only Reviewer. Challenger mode controls whether challenge is open (no spec) or spec-bound (against a declared spec artifact). Do NOT invoke to issue a verdict or score — that is Grader's job. Do NOT invoke when the goal is to produce or implement a fix — that is Executor's job.
Root cause investigation using structured analysis methods. 5-whys, fishbone, fault-tree. Knowledge-graph-leveraged when Nexus is available. On-demand.
API lifecycle management. Version, deprecate, audit contracts, enforce backward compatibility. Four modes: --version, --deprecate, --contract, --audit.
Gateway routing engine. Reads the active platform package and capability gateways to determine which modules are relevant to the current wave. Assembles multi-module context using Economy placement rules. Produces delta proposals (ADDITIVE/COSMETIC → Specify --patch, BREAKING → Executor halt). Writes only to product space — never touches .wabblespec/ (I11).
Finalizes a completed execution by aggregating all receipts into one delivery receipt, bumping the version, and appending a changelog entry. A task is not done until Archive runs.
Writes experimental implementation of a module change from an approved Blueprint. For AUGMENT type: completes a modified copy of the existing module. For NEW type: completes Factory stubs. All output goes to .wabblespec/state/experiments/augments/. Never touches production module space.