FeatBit Experimentation

This skill is the single entry point for the FeatBit release-decision loop:

intent -> hypothesis -> implementation -> exposure -> measurement -> interpretation -> decision -> learning -> next intent

It replaces the old multi-skill layout (featbit-release-decision, intent-shaping, hypothesis-design, reversible-exposure-control, measurement-design, experiment-workspace, evidence-analysis, learning-capture, and project-sync). Do not call those split skills from this workflow. Treat their former behavior as internal stages of this skill.

Core Principles

• Do not let an available tool define the user's problem before the decision type is clear.
• Do not implement before the business intent and hypothesis are explicit.
• Do not expose a measurable change before reversibility and rollout rules are defined.
• Do not measure with multiple primary metrics. One metric decides; guardrails protect.
• Do not interpret experiment data before sufficiency, SRM, instrumentation, and window checks pass.
• Do not close a cycle without recording a reusable learning and a next hypothesis.
• Persist every stage transition through the configured FeatBit experimentation MCP server.